---
title: "Cancel triggered event"
method: DELETE
path: "/v1/events/trigger/{transactionId}"
tags: ["Events"]
---

# Cancel triggered event

`DELETE /v1/events/trigger/{transactionId}`

## Request

- Base URL: `https://api.notifly.io`
- URL: `https://api.notifly.io/v1/events/trigger/{transactionId}`
- Auth: API key in header `Authorization`

Using a previously generated transactionId during the event trigger,
     will cancel any active or pending workflows. This is useful to cancel active digests, delays etc...

## Path parameters

- `transactionId` string, required

## Response `200`

- boolean

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `405`: Method Not Allowed
- `409`: Conflict
- `413`: Payload Too Large
- `414`: URI Too Long
- `415`: Unsupported Media Type
- `422`: Unprocessable Entity
- `429`: The client has sent too many requests in a given amount of time.
- `500`: Internal Server Error
- `503`: The server is currently unable to handle the request due to a temporary overload or scheduled maintenance, which will likely be alleviated after some delay.

---

[API](https://skmtc.dev/notifly/apis/notifly-api.md) · [All operations](https://skmtc.dev/notifly/apis/notifly-api/llms.txt) · [OpenAPI document](https://skmtc.dev/notifly/apis/notifly-api/revisions/af909b9e1e57?raw)