Endpoint
Authentication
Requires a Personal API Access Token.Header
Request
Headers
| Header | Value | Required |
|---|---|---|
| Authorization | Bearer | Yes |
| Content-Type | application/json | Yes |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
| policyName | string | Yes | Policy name (must exist) |
Request Body
Full JSON Body Example
Request Body Fields
The request body structure is identical to Add Policy. See that documentation for complete field descriptions.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 updating policy |
| deployTargetEnvironmentNameList | array | No | [] | List of environment names to deploy to |
| order | integer | No | null | Policy execution order (starts from 1). If null, keeps existing order. If >= list size, moves to end |
order is null, the policy keeps its existing position. If order is provided, the policy is moved to that position.
EnumPolicyTargetScope
ALL- Policy applies to all endpointsENDPOINT- Policy applies only to specified endpoint
EnumPolicyTargetPipeline
REQUEST- Executes in request pipelineRESPONSE- Executes in response pipelineERROR- Executes in error pipeline
EnumHttpRequestMethod
GET,POST,PUT,DELETE,PATCH,OPTIONS,HEAD,TRACE,ALL
policy
The policy object structure is identical to Add Policy. All policy fields can be updated. Important: The policytype cannot be changed. If you need a different policy type, delete the existing policy and create a new one.
Response
Success Response (200 OK)
deploy: true is set in the request, the response includes deployment result:
Response Fields
| Field | Type | Description |
|---|---|---|
| status | string | Response status: SUCCESS or FAILURE |
| deploymentResult | object | Deployment result (if deploy=true). See Deployment Result Object |
Deployment Result Object (deploymentResult)
| Field | Type | Description |
|---|---|---|
| success | boolean | Overall deployment success status |
| responseTime | integer | Total deployment response time in milliseconds |
| detailList | array | List of deployment details per pod/environment |
Deployment Detail Object (detailList item)
| Field | Type | Description |
|---|---|---|
| envName | string | Environment name |
| podName | string | Pod name where deployment occurred |
| podIp | string | Pod IP address |
| success | boolean | Deployment success status for this pod |
| responseTime | integer | Deployment response time for this pod in milliseconds |
EnumStatus
SUCCESS- Operation successfulFAILURE- Operation failed
Error Response (400 Bad Request)
Common Causes
- Policy name does not exist
- Invalid targetScope (ENDPOINT without targetEndpoint)
- Invalid targetEndpoint (endpoint not found in API Proxy)
- Invalid policy type (cannot change policy type)
- Missing required policy fields
- Invalid condition configuration
- Invalid order value (order < 1)
Error Response (401 Unauthorized)
Error Response (404 Not Found)
cURL Example
Example 1: Update Policy Configuration
Example 2: Update Policy Order
Move a policy to a different position in the pipeline.Example 3: Update Policy Scope
Move a policy from ALL endpoints to a specific endpoint.Example 4: Update Policy Pipeline
Move a policy from REQUEST pipeline to RESPONSE pipeline.Permissions
- User must have
API_MANAGEMENT+MANAGEpermission in the project - If
deploy: trueis set in the request, user must also haveAPI_MANAGEMENT+DEPLOY_UNDEPLOYpermission
Notes and Warnings
- Policy Name: Policy name cannot be changed. Use Delete and Add to rename a policy.
- Policy Type: Policy type cannot be changed. Use Delete and Add to change policy type.
- Order: If
orderis null, the policy keeps its existing position. Iforderis provided, the policy is moved to that position (1-based indexing). - Scope Change: You can change
targetScopefrom ALL to ENDPOINT or vice versa. Ensure the endpoint exists if using ENDPOINT scope. - Pipeline Change: You can change
targetPipeline(REQUEST, RESPONSE, ERROR). The policy will be moved to the new pipeline. - Deployment: If
deploy: true, ensure environments exist and user has deployment permissions. - Validation: All policy-specific validations apply. See individual policy documentation for required fields.
Related Documentation
- Add Policy - Add a new policy
- Delete Policy - Delete a policy
- List Policies - List all policies
- Policy API Based Throttling - Example policy documentation

