Endpoint
Authentication
Requires a Personal API Access Token.Header
Request
Headers
| Header | Value | Required |
|---|---|---|
| Authorization | Bearer | Yes |
| Content-Type | application/json | Yes |
Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| projectName | string | Yes | Project name |
| apiProxyName | string | Yes | API Proxy name |
Request Body
Full JSON Body Example
Request Body Fields
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| errorHandlingType | string | No | DEFAULT | Error handling strategy. See EnumErrorHandlingType |
| statusCodeList | array[integer] | No | - | List of HTTP status codes that trigger custom error handling |
| customizeErrorMessageEnabled | boolean | No | false | Enable custom error messages for matching status codes |
| errorMessageList | array[object] | No | - | List of custom error message definitions. See Error Message Object |
EnumErrorHandlingType
DEFAULT- Use default error handling (pass through backend errors)ADVANCED- Advanced error handling with full customizationSTATUS_CODE_LIST- Custom handling for specific HTTP status codes only
Error Message Object
| Field | Type | Required | Description |
|---|---|---|---|
| httpStatusCode | integer | Yes | Original HTTP status code to match |
| customizedHttpStatusCode | integer | No | Replacement HTTP status code to return to client |
| customizedErrorCode | string | No | Custom error code string |
| customizedMessage | string | No | Custom error message text |
Response
Success Response (200 OK)
Error Response (401 Unauthorized)
Error Response (404 Not Found)
cURL Example
Example 1: Configure Status Code Based Error Handling
Example 2: Reset to Default Error Handling
Example 3: Enable Advanced Error Handling with Custom Messages
Notes and Warnings
- Error Handling Types:
DEFAULT: Backend error responses are passed through to the client without modificationADVANCED: All backend errors are intercepted and custom error messages are appliedSTATUS_CODE_LIST: Only the specified HTTP status codes trigger custom error handling
- Custom Messages: When
customizeErrorMessageEnabled=true, matching errors use the customized message and status code - Error Message Matching: Error messages are matched by
httpStatusCode— if a backend returns a status code in the list, the corresponding custom message is used - Partial Updates: You can update individual fields without affecting others
Permissions
User must haveAPI_MANAGEMENT + MANAGE permission in the project.
Related Documentation
- Update JSON Error Template - Configure JSON error response template
- Update XML Error Template - Configure XML error response template
- Update Custom Message - Configure custom response message

