Authentication
Send an API key as a bearer token. The key must carry the links.edit permission; a key without it is refused with 403, not 404.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X DELETE https://api.zinndigital.com/v1/ai/recipes/{recipeId} \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Archived rather than removed, and its schedule cleared in the same write. Runs it already produced stay readable — they point at content that exists. Requires `links.edit`.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
recipeId (path) | Uuid | Yes | — |
Errors this endpoint can return
401 · 403 · 404 · 429