Ana içeriğe atla

Endpoint

Authentication

Requires a Personal API Access Token.

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 method
  • POST - HTTP POST method
  • PUT - HTTP PUT method
  • HEAD - HTTP HEAD method
  • OPTIONS - HTTP OPTIONS method
  • DELETE - HTTP DELETE method
  • PATCH - HTTP PATCH method
  • TRACE - HTTP TRACE method
  • ALL - All HTTP methods

Header Object (headerList)

Notes

  • At least one of relativePathList, methodList, hostList, or headerList must be provided
  • If relativePathList is provided, all paths must be at least 2 characters long
  • Route matching is done using AND logic: all specified conditions must match
  • bufferRequest and bufferResponse control 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)

When 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 ALL to match all HTTP methods
    • Method matching is case-insensitive
  • Host Matching:
    • Host names are matched against the Host header
    • Host matching is case-insensitive
  • 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, or headerList must be provided
    • Empty lists are treated as null
  • Deploy:
    • When deploy is set to true, the API proxy will be deployed to the specified environments after saving changes
    • deployTargetEnvironmentNameList is required when deploy=true
    • If deployment fails for some environments, successfully deployed environments are still reported in the response

Permissions

User must have API_MANAGEMENT + MANAGE permission in the project.
  • Deployment:
    • Changes take effect after deployment
    • Undeployed changes do not affect routing