Ana içeriğe atla

Endpoint

Authentication

Requires a Personal API Access Token.

Request

Headers

Path Parameters

Request Body

Full JSON Body Example

Request Body Fields

forwardedIpHeaderParam Fields

EnumPolicyXFFOrder

  • FIRST - Use first IP address in X-Forwarded-For header
  • SECOND - Use second IP address in X-Forwarded-For header
  • THIRD - Use third IP address in X-Forwarded-For header
  • FOURTH - Use fourth IP address in X-Forwarded-For header
  • FIFTH - Use fifth IP address in X-Forwarded-For header
  • LAST - Use last IP address in X-Forwarded-For header
Note: All fields are optional. Only provided fields are updated.

X-Forwarded-For Header

The X-Forwarded-For header contains a comma-separated list of IP addresses:
The xffOrder determines which IP address is used:
  • FIRST - Uses client-ip (original client)
  • LAST - Uses proxy2-ip (last proxy)
  • SECOND, THIRD, etc. - Uses IP at specified position

Response

Success Response (200 OK)

When deploy=true is specified:

Response Fields

Error Response (400 Bad Request)

Error Response (401 Unauthorized)

Error Response (404 Not Found)

cURL Example

Example 1: Enable Forwarded IP Header

Example 2: Use Custom Header Name

Example 3: Save and Deploy

Notes and Warnings

  • Header Name: Default is X-Forwarded-For. Can be customized (e.g., X-Real-IP)
  • IP Order: FIRST gets original client IP, LAST gets last proxy IP
  • Use Cases:
    • Forward client IP for logging/analytics
    • Forward client IP for rate limiting
    • Forward client IP for geolocation
  • Chain: X-Forwarded-For contains comma-separated IP chain
  • Deploy: When deploy=true, the API proxy is automatically deployed to the specified environments after saving

Permissions

User must have API_MANAGEMENT + MANAGE permission in the project.