Endpoint
Authentication
Requires a Personal API Access Token.Header
Request
Headers
Path Parameters
Request Body
Full JSON Body Example - Update OpenAPI
Full JSON Body Example - Update WSDL
Full JSON Body Example - Update Reverse Proxy
Request Body Fields
EnumApiProxySpecType (apiProxyCreationType)
OPEN_API- OpenAPI 3.0 specificationSWAGGER- Swagger 2.0 specificationWSDL- WSDL specification (SOAP)REVERSE_PROXY- Reverse proxy (no specification)
ClientRoute (clientRoute)
RoutingInfo (routingInfo)
RoutingAddress (routingInfo.routingAddressList item)
MaintenanceModeSetting (maintenanceModeSetting)
SpecAuthorizationValue (specAuthorizationValueList item)
Notes
apiProxyNamemust exist (API Proxy will be updated, not created).apiProxyCreationTypemust match the existing API Proxy type (cannot change type).specUrlis required unlessapiProxyCreationTypeisREVERSE_PROXY.clientRoute.relativePathListmust contain at least one path, and the first path cannot be empty.reParse: trueis recommended for updates to reparse the specification.soapToRestcannot be enabled if the API Proxy was not created with this option initially.- If
apiProxyDescriptionis empty, the existing description is preserved. routingInfois optional; if not provided, existing routing settings are preserved.
Response
Success Response (200 OK)
cURL Example
Notes and Warnings
- Update vs Create:
- This endpoint updates an existing API Proxy (identified by
apiProxyName) - If API Proxy does not exist, it will be created
- Use this endpoint to reparse and update API Proxy from specification URL
- This endpoint updates an existing API Proxy (identified by
- Type Restrictions:
apiProxyCreationTypemust match the existing API Proxy type- Cannot change from SOAP to REST or vice versa
- Cannot enable
soapToRestif not enabled initially
- Reparsing:
reParse: truere-parses the specification and updates endpoints- Existing endpoints may be modified or removed if specification changes
- Policies and settings are preserved during reparse
- Client Route:
clientRoute.relativePathListmust contain at least one path- First path in the list cannot be empty
- Virtual hosts are optional
- Routing:
routingInfois optional- If not provided, existing routing settings are preserved
- Can update routing addresses, weights, and health checks
- Deployment:
- Set
deploy: trueto automatically deploy after update - Specify
deployTargetEnvironmentNameListfor target environments - Requires
API_MANAGEMENT+DEPLOY_UNDEPLOYpermission if deploying
- Set
Permissions
User must haveAPI_MANAGEMENT + MANAGE permission in the project. For deployment operations (when deploy: true is set), user must also have API_MANAGEMENT + DEPLOY_UNDEPLOY permission.
- Specification Authorization:
- Use
specAuthorizationValueListif specification URL requires authentication - Common: Authorization header with Bearer token
- Headers are sent when fetching specification
- Use
Related Documentation
- Create API Proxy from URL - Create new API Proxy from URL
- Update API Proxy - Update API Proxy metadata
- Deploy API Proxy - Deploy API Proxy to environments

