Ana içeriğe atla

Endpoint

Alternative Endpoint (PUT for update)

Authentication

Requires a Personal API Access Token.

Request

Headers

Path Parameters

Form Data

Request Body (metadata JSON)

Full JSON Body Example

Request Body Fields

EnumApiProxySpecType

  • OPEN_API - OpenAPI 3.0 specification
  • SWAGGER - Swagger 2.0 specification
  • WSDL - WSDL specification (SOAP)
  • REVERSE_PROXY - Reverse proxy (no spec file)
Note: For REVERSE_PROXY, specFile is not required.

clientRoute

EnumHttpRequestMethod

  • GET, POST, PUT, DELETE, PATCH, OPTIONS, HEAD, TRACE, ALL

routingInfo

EnumRoutingAlgorithm

  • ROUND_ROBIN - Round-robin load balancing
  • LRU - Least recently used
  • WEIGHTED - Weighted load balancing (requires weight in routingAddressList)
  • RANDOM - Random selection
  • PICK_FIRST - Pick first available

routingAddressList Item

EnumSoapApiPortType

  • SOAP11 - SOAP 1.1
  • SOAP12 - SOAP 1.2

maintenanceModeSetting

Response

Success Response (200 OK)

Response Fields

Error Response (400 Bad Request)

Common Causes

  • API Proxy name already exists
  • Invalid specification file format
  • Invalid API creation type
  • Missing required fields (clientRoute, specFile)
  • Invalid file format

Error Response (401 Unauthorized)

Error Response (404 Not Found)

cURL Example

Example 1: Create REST API Proxy from OpenAPI File

Example 2: Create SOAP API Proxy from WSDL File

Example 3: Create API Proxy with WSDL ZIP File

For WSDLs with many XSDs, use a ZIP file:

Example 4: Update API Proxy (Reparse) using PUT

Permissions

User must have API_MANAGEMENT + MANAGE permission in the project. For deployment operations (when deploy: true is set), user must also have API_MANAGEMENT + DEPLOY_UNDEPLOY permission.

Notes and Warnings

  • File Format: Supported formats: OpenAPI 3.0 (JSON/YAML), Swagger 2.0 (JSON/YAML), WSDL (XML)
  • ZIP Files: For WSDLs with many XSDs, use a ZIP file containing all related files
  • Unique Names: API Proxy names must be unique within a project
  • Reparse: Use PUT endpoint with reParse: true to update an existing API proxy from a new specification file
  • Type Consistency: When reparsing, the API creation type must match the original type
  • SOAP Features: enableWSA and enableWSRM are only applicable for SOAP APIs
  • Reverse Proxy: For reverse proxy, specFile is not required
  • Deployment: If deploy: true, ensure environments exist and user has deployment permissions
  • License Limits: Creating API proxies may be subject to license limits
  • File Size: Large specification files may take longer to process