Discard an open count and every line in it
Deletes an open count and its lines outright. Takes no body, and answers 204 with none.
Only an open count can be discarded. A posted count is refused 400. It is a record of what a warehouse found on a date, and deleting it would remove the evidence behind every variance figure measured from it. To correct a posted count, open a new one.
Nothing about stock changes either way: an open count has never moved a level, so discarding it leaves the shelf exactly as it was.
This is not the way to close a count. post_stocktake records what was found; this throws it away, and a count discarded by mistake has to be created and counted again from nothing.
Scope: stocktakes:write, which includes stocktakes:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/stocktakes/{stocktake_id}
- Auth: HTTP bearer
Path parameters
The open count to discard.
Headers
The date train to answer on. One train exists today, 2026-11, the one this reference describes and the one every key is minted on, so the call answers on it with or without this header. Send it anyway, so a client built now names its train from the start.
A string of your own, up to 255 characters, that makes this write safe to retry. Send the same key twice and the second request is answered with the first one's status and body instead of writing again, so a client that retried after a timeout ends holding the record's id rather than creating a second one. Reusing a key with a different body, or while the first request is still running, is refused 409. A write that failed releases its key. Keys answer for 24 hours and belong to the API key that used them. A key longer than 255 characters is ignored and the write goes ahead without the guarantee.
Response
The count and its lines are gone. No body.
Changes
No recorded changes to this operation across all 1 revision of this API.