General Information
Policy Type
UI Documentation
📖 For detailed information: [UI Documentation Link - Link will be added here]
Endpoints
List Policies
Add Policy
Update Policy
Delete Policy
List Policies
Endpoint
Request
Headers
| Header | Value |
|---|---|
| Authorization | Bearer {token} |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
Response
Success Response (200 OK)
cURL Example
Add Policy
Endpoint
Request
Headers
| Header | Value |
|---|---|
| Authorization | Bearer {token} |
| Content-Type | application/json |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
| policyName | string | Yes | Policy name |
Request Body
Full JSON Body Example
Request Body Fields
operationMetadata
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| targetScope | string | Yes | - | Policy scope: ALL or ENDPOINT |
| targetEndpoint | string | No* | - | Endpoint path (required if targetScope=ENDPOINT) |
| targetEndpointHTTPMethod | string | No* | - | HTTP method (required if targetScope=ENDPOINT) |
| targetPipeline | string | Yes | - | Pipeline: REQUEST, RESPONSE, or ERROR |
| deploy | boolean | No | true | Whether to deploy after adding policy |
| deployTargetEnvironmentNameList | array | No | [] | List of environment names to deploy to |
| order | integer | No | null | Policy execution order (starts from 1) |
ALL- Policy applies to all endpointsENDPOINT- Policy applies only to specified endpoint
REQUEST- Executes in request pipeline (validates request body)RESPONSE- Executes in response pipeline (validates response body)ERROR- Executes in error pipeline
GET,POST,PUT,DELETE,PATCH,OPTIONS,HEAD
policy
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| type | string | Yes | - | Policy type: policy-json-schema-validation |
| description | string | No | - | Policy description |
| active | boolean | No | true | Whether policy is active |
| pathForBody | string | Yes | - | JSONPath expression to locate JSON body to validate |
| schemaDefinitionList | array | Yes | - | List of JSON schema definitions (at least one required) |
JSONPath Examples
$- Root of JSON document$.data- Data property at root$.users[0]- First element in users array$.request.body- Nested path
Note
pathForBodymust be a valid JSONPath expression.schemaDefinitionListmust contain at least one schema definition.
schemaDefinitionList
Each schema definition is an object with the following fields:| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| schemaNo | integer | No | 0 | Schema number (for ordering multiple schemas) |
| schemaBody | string | Yes | - | JSON Schema definition (JSON string) |
| systemId | string | No | null | System ID for schema reference |
| targetNamespace | string | No | null | Target namespace (for XML compatibility) |
| rootSchema | boolean | No | false | Whether this is the root schema |
JSON Schema Format
TheschemaBody must be a valid JSON Schema (draft-07 or compatible). Example:
Response
Success Response (200 OK)
cURL Example
Update Policy
Endpoint
Request
Headers
| Header | Value |
|---|---|
| Authorization | Bearer {token} |
| Content-Type | application/json |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
| policyName | string | Yes | Policy name |
Request Body
Full JSON Body Example
Response
Success Response (200 OK)
cURL Example
Delete Policy
Endpoint
Request
Headers
| Header | Value |
|---|---|
| Authorization | Bearer {token} |
| Content-Type | application/json |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
| policyName | string | Yes | Policy name |
Request Body
Full JSON Body Example
Request Body Fields
operationMetadata
| Field | Type | Required | Description | |
|---|---|---|---|---|
| targetScope | string | Yes | Policy scope: ALL or ENDPOINT | |
| targetPipeline | string | Yes | Pipeline: REQUEST, RESPONSE, or ERROR | |
| deploy | boolean | No | false | Whether to deploy after deletion |
Response
Success Response (200 OK)
cURL Example
Notes and Warnings
-
JSONPath:
pathForBodymust be a valid JSONPath expression pointing to the JSON to validate -
Schema Definition:
schemaDefinitionListmust contain at least one schema definition -
JSON Schema:
schemaBodymust be a valid JSON Schema (draft-07 or compatible) -
Schema Number:
schemaNois used for ordering when multiple schemas are defined -
Root Schema: Set
rootSchema: truefor the primary schema - Validation Failure: When validation fails, the request/response is rejected with an error
- Performance: Schema validation adds processing overhead. Use for critical validation only.
-
Pipeline:
REQUESTpipeline validates request body before processingRESPONSEpipeline validates response body before sending to client
- Error Messages: Configure error messages in the policy to customize validation error responses
-
Deployment: Policy changes require deployment to take effect. Set
deploy: trueor deploy manually.
Related Documentation
- List Policies - List all policies
- Add Policy - General policy addition guide
- Update Policy - General policy update guide
- Delete Policy - General policy deletion guide

