Endpoint
Authentication
Requires a Personal API Access Token.Header
Request
Headers
Path Parameters
Request Body
Full JSON Body Example
Request Body Fields
grpcSettings Fields
Note: All fields are optional. Only provided fields are updated. Default values are inherited from system settings.
Response
Success Response (200 OK)
deploy=true is specified:
Response Fields
Error Response (400 Bad Request)
Error Response (401 Unauthorized)
Error Response (404 Not Found)
cURL Example
Example 1: Configure Message Size and Keep-Alive
Example 2: Configure Retry and Hedging
Example 3: Configure Channel Idle Timeout
Example 4: Save and Deploy
Notes and Warnings
- gRPC Only: This endpoint is only applicable to API Proxies with gRPC type. Using it on HTTP/REST proxies will result in an error.
- Message Size:
maxInboundMessageSizelimits the size of individual gRPC messages. Increase for large payloads (e.g., file uploads). - Keep-Alive: Keep-alive pings maintain the connection to the backend.
keepAliveWithoutCalls=truekeeps the connection alive even when no RPCs are active. - Retry vs Hedging: Retry attempts are sequential (retry after failure), hedged attempts are parallel (send multiple copies simultaneously).
- Buffer Limit:
perRpcBufferLimitcontrols how much data can be buffered per RPC — relevant for retries and hedging. - System Defaults: When a field is not set, the value is inherited from system-level settings.
- Deploy: When
deploy=true, the API proxy is automatically deployed to the specified environments after saving
Permissions
User must haveAPI_MANAGEMENT + MANAGE permission in the project.
Related Documentation
- Update Connection Settings - Update HTTP connection settings
- Update Routing Addresses - Update backend routing addresses
- Get API Proxy - Get API proxy details

