Update a Custom API Entry using the settings endpoint
PUT/v2/settings/extensions/custom-apis/:custom_api_id/entries/:custom_api_entry_id
Update a Custom API Entry using the settings endpoint
Request
Responses
- 200
- 201
- 400
- 404
- 409
- 412
- 413
- 500
OK
Response Headers
ETag string
A unique identifier representing the current version of the resource. When the resource changes, the ETag value will also change.
Created
Response Headers
ETag string
A unique identifier representing the current version of the resource. When the resource changes, the ETag value will also change. The ETag hash will be the same value as `etag_id`, and is marked as a weak entity tag string. For example: etag: W/"5feceb66ffc86f38d952786c6d696c79c2dbc239dd4e91b46729d73a27fb57e9", etag_id: 5feceb66ffc86f38d952786c6d696c79c2dbc239dd4e91b46729d73a27fb57e9
Bad request. The request failed validation.
Not found. The requested entity does not exist.
Unable to perform the operation at this time.
Precondition Failed.
Payload Too Large. The total size of a Custom API Entry must not exceed 64KB.
Internal server error. There was a system failure in the platform.