Skip to content

#195 · Asset Delete Now Returns Its Documented Response

Availability: General Availability

DELETE /assets/{assetId} now answers with the response the API reference has always documented. Clients generated from the OpenAPI specification decode a successful delete without a workaround.

What's New

  • A documented body on success: DELETE /assets/{assetId} returns {"message": "Asset deleted successfully"} with 200, the same shape as the other delete endpoints.

Breaking Changes

  • The response body changed shape (API): the endpoint used to return a bare JSON boolean (true), which didn't match the published schema. It now returns an object with a message string. Scripts that read the body as a boolean must read the status code instead: 200 means the asset was deleted.
  • Nothing changes for the CLI and the MCP server: escape-cli assets delete accepts both shapes.

How to Get Started

  • API: treat 200 as success, and stop parsing the body as a boolean. curl -X DELETE -H "Authorization: Key $ESCAPE_API_KEY" https://public.escape.tech/v3/assets/00000000-0000-0000-0000-000000000000

Public API Docs →

Questions?

Have a question? Reach out on your dedicated support channel, or email us at support@escape.tech.