Delete a custom code block
/settings/custom-code/{custom_code_id}Moves the custom code block to the trash instead of permanently deleting it.
A block in the trash can be restored with the update operation by sending deleted: false.
Autonomous mode: the API credential secret, sent as a bearer token. Credential secrets are identified by a fixed prefix.
In: header
Path Parameters
Public ID of the custom code, prefixed with cc_.
Header Parameters
Client-generated key that makes the request safe to retry. Must be 1 to 128 characters from [A-Za-z0-9._:-]. Optional on this operation; when sent, a malformed key returns idempotency_key_invalid, and repeating the request with the same key and the same body returns the stored result with Idempotent-Replayed: true.
Optional client-generated identifier of the request, up to 64 characters from [A-Za-z0-9._-]. Echoed back in the response and recorded in the request log; it never replaces the server-generated X-Request-Id.
length <= 64Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X DELETE "https://example.com/settings/custom-code/string"Update a custom code block PATCH
Updates an existing custom code block. Only the fields present in the request are changed. Changing `status` also requires the `custom_code.activate` permission. Changing the `name` or `content` of a `pushalertco` block also requires the `custom_code.manage_pwa` permission. Send `deleted: false` to restore a block from the trash. Send the `ETag` returned by the retrieve operation in the `If-Match` header to avoid overwriting changes made since the block was retrieved.
Configuration3
Next Page