Cancel a trigger
Cancel a trigger by sending a DELETE request to /cancel with either ttr-trigger-idheader or ttr-custom-keyheader.
The same endpoint cancels both one-shot triggers and recurring triggers (cron generators). The lookup tries generators first, then falls back to one-shot triggers — which is unambiguous because the custom-key namespace is shared (see Custom trigger keys).
Request headers
| Header | Required | Description |
|---|---|---|
ttr-api-keyheader | Yes | Your API key |
ttr-trigger-idheader | One of these | The trigger or generator ID to cancel |
ttr-custom-keyheader | One of these | The custom key of the trigger or generator to cancel |
Provide exactly one of ttr-trigger-idheader or ttr-custom-keyheader, not both.
Cancelling a recurring trigger
Cancelling a generator stops it from producing future instances. The currently-pending instance (the next scheduled run) is also cancelled in the same operation. Past instances — whether already executed, running, or completed — are kept untouched.
Status codes
| Status code | Meaning |
|---|---|
| 204No Content | Trigger cancelled successfully |
| 400Bad Request | Bad request (missing or conflicting identifiers) |
| 401Unauthorized | Invalid API key |
| 404Not Found | Trigger not found |
| 410Gone | Trigger already executed or cancelled |