Endpoint
Authentication
Requires a Personal API Access Token.Header
Request
Headers
Path Parameters
Request Body
Full JSON Body Example - Path-Based Routing
Full JSON Body Example - Host-Based Routing
Full JSON Body Example - Header-Based Routing
Full JSON Body Example - Combined Routing
Request Body Fields
clientRoute Fields
EnumHttpRequestMethod (methodList)
GET- HTTP GET methodPOST- HTTP POST methodPUT- HTTP PUT methodHEAD- HTTP HEAD methodOPTIONS- HTTP OPTIONS methodDELETE- HTTP DELETE methodPATCH- HTTP PATCH methodTRACE- HTTP TRACE methodALL- All HTTP methods
Header Object (headerList)
Notes
- At least one of
relativePathList,methodList,hostList, orheaderListmust be provided - If
relativePathListis provided, all paths must be at least 2 characters long - Route matching is done using AND logic: all specified conditions must match
bufferRequestandbufferResponsecontrol whether request/response bodies are buffered in memory- Buffering enables policies to access and modify request/response bodies
- Disabling buffering improves performance but limits policy capabilities
Response
Success Response (200 OK)
deploy=true is specified:
Response Fields
Error Response (400 Bad Request)
Common Causes
- All route lists are empty or null
- Relative paths are less than 2 characters
- Invalid HTTP method values
- Invalid header format
Error Response (401 Unauthorized)
Error Response (404 Not Found)
cURL Example
Example 1: Path-Based Routing
Example 2: Host-Based Routing
Example 3: Header-Based Routing
Example 4: Combined Routing
Example 5: Save and Deploy
Notes and Warnings
- Route Matching:
- Route matching uses AND logic: all specified conditions must match
- If multiple lists are provided, the request must match all of them
- Relative Paths:
- Paths must be at least 2 characters long
- Paths are matched against the request URI path
- Path matching is case-sensitive
- HTTP Methods:
- Use
ALLto match all HTTP methods - Method matching is case-insensitive
- Use
- Host Matching:
- Host names are matched against the
Hostheader - Host matching is case-insensitive
- Host names are matched against the
- Header Matching:
- Header names are case-insensitive
- Header values are matched exactly (case-sensitive)
- All specified headers must be present in the request
- Buffering:
bufferRequest: true- Enables request body access in policies (required for request transformation)bufferResponse: true- Enables response body access in policies (required for response transformation)- Disabling buffering improves performance but limits policy capabilities
- At Least One Route:
- At least one of
relativePathList,methodList,hostList, orheaderListmust be provided - Empty lists are treated as null
- At least one of
- Deploy:
- When
deployis set totrue, the API proxy will be deployed to the specified environments after saving changes deployTargetEnvironmentNameListis required whendeploy=true- If deployment fails for some environments, successfully deployed environments are still reported in the response
- When
Permissions
User must haveAPI_MANAGEMENT + MANAGE permission in the project.
- Deployment:
- Changes take effect after deployment
- Undeployed changes do not affect routing
Related Documentation
- Get API Proxy - Get API proxy details
- Update API Proxy - Update API proxy configuration
- Deploy API Proxy - Deploy API proxy

