Cancel cards
Cancelling a card means that the (open) state of card will be changed to (closed) state of cancelled. A cancelled card will no longer show in your customer's card stream. Open state cards include those with a status of snoozed or embargoed.
You can read more about card states in the Card lifecycle model guide.
There are 2 ways to cancel cards: from within the Workbench, or by using the API. This guide explains both approaches.
Cancel cards from the Workbench
The Cancel Cards tool is available in the Tools section of the Workbench. Everyone can see the tool, but only those with the required permission can use it.

In the Cancel Cards tool, you can apply one or more criteria to the cards you want to cancel. Cards must match all criteria to be cancelled.

Before the card cancellation begins, you'll be shown an estimate of the number of cards that will be cancelled.

Tracking a cancellation
While a cancellation is in progress, the tool shows how many cards have been cancelled so far, and updates as more are cancelled. Because a large cancellation runs in batches, the total number of matching cards isn't known until the last batch begins.
Stopping a cancellation
To stop a cancellation that is still in progress, click Stop on the in-progress cancellation. No further batches will start.
The batch that is already in progress when you stop may still be cancelled in full, so the number of cancelled cards can keep rising for a while after you stop. A single batch is up to 250,000 cards. Once a cancellation has stopped, it's marked as stopped and shows how many cards were cancelled before it stopped.
To cancel the remaining cards later, start a new cancellation with the same criteria. Only cards that are still active, snoozed or embargoed will match.
Cancel cards using the Cards API
It is also possible to cancel cards using the Cards API, as explained in the cancel cards section of the Cards API guide.
The API works the same way as the workbench tool:
- Cancellations run in batches of up to 250,000 cards until every matching card is cancelled.
- The
publishedAfterandpublishedBeforequery parameters take ISO 8601 timestamps and limit the cancellation to cards published within that range. - A cancellation in progress can be stopped with
POST /v1/{environmentId}/cards/cancel-stop/{cancelTaskId}. Its status then becomesstopped. Stopping a cancellation that has already finished returns a409error.
The same applies to dismissing and completing cards in bulk, using the dismiss-stop and complete-stop endpoints. See the Atomic API spec for full details.
Set up Insomnia
If you prefer to use a third-party tool to interact with the Atomic API, look at the Using Insomnia guide.
To cancel cards, make sure you have followed the guide and sent yourself a card successfully using Insomnia. This means that you have correctly configured everything that's needed:
- you have configured all Insomnia environment variables correctly
- you have set up authentication controls
- you have an access token
- you have an Events scoped token
Cancel cards using Insomnia
- Select the request titled Cancel cards from your collection.
- Click on the 'query' tab. You can now see the URL preview and a list of possible query parameters. By default, none of these parameters has their checkbox ticked, which means the cancel request is not scoped in any way.
You can combine multiple parameters, or only use one. Always make sure you tick the checkbox, and provide a value next to the parameter name.

The screenshot above shows how to cancel all cards sent to a specific userId.
You must set the correct userId value before you hit Send. If your request is successful, you will receive a response containing a link to the cancel-status endpoint. This endpoint can then be called to view the status of the cancellation job.
FAQs
Will cards sent after I start a cancellation be cancelled?
No. A cancellation only includes cards that were created before it started, so a cancellation whose criteria keep matching newly sent cards still finishes. To cancel cards sent since then, start another cancellation.
Why is my cancellation still running after I clicked Stop?
Stopping prevents any further batches from starting, but the batch already in progress may still be cancelled in full. The count of cancelled cards can keep rising until that batch finishes.
Why weren't embargoed cards cancelled when I used a published date?
Embargoed cards haven't been published yet, so they have no published date and don't match the Published after or Published before fields. To cancel them, run a cancellation without the published date fields.
Why does the review show 250,000+ instead of an exact number?
The review counts up to 250,000 matching cards. When more cards than that match, it shows 250,000+. Every matching card is still cancelled.
Can I cancel more than 250,000 cards at once?
Yes. Larger cancellations are split into batches of up to 250,000 cards and run one after another automatically. You don't need to start the cancellation again.