ApiConfigLimits
{
"num_api_paths": 0,
"num_api_paths_per_policy": 0,
"num_api_schemas": 0,
"num_api_schemas_per_policy": 0,
"num_apis": 0,
"num_schema_nesting": 0
}Maximum total number of API path objects allowed across the system. Field introduced in 32.1.4. Allowed with any value in Enterprise, Essentials, Basic, Enterprise with Cloud Services edition.
Maximum number of API path definitions (unique URL path patterns) that can be configured for a single API policy. Field introduced in 32.1.4. Allowed with any value in Enterprise, Essentials, Basic, Enterprise with Cloud Services edition.
Maximum total number of API schema objects allowed across the system. Field introduced in 32.1.4. Allowed with any value in Enterprise, Essentials, Basic, Enterprise with Cloud Services edition.
Maximum number of API schema objects that can be associated with a single API policy. Field introduced in 32.1.4. Allowed with any value in Enterprise, Essentials, Basic, Enterprise with Cloud Services edition.
Maximum total number of API endpoints allowed across the system. Each ApiPath can have up to 7 ApiEndpoints. Field introduced in 32.1.4. Allowed with any value in Enterprise, Essentials, Basic, Enterprise with Cloud Services edition.
Maximum allowed nesting depth of JSON schema definitions within an API policy. Schema structures that exceed this depth will be rejected at config time. In the datapath, JSON payloads with greater nesting depth will not be parsed. Field introduced in 32.1.4. Allowed with any value in Enterprise, Essentials, Basic, Enterprise with Cloud Services edition.