Delete an execution | INFONITE

Delete an execution and everything retrieved under it.

This is a purge, not an archive: the execution, its state, its records and its attachments are removed and cannot be recovered. Call it as soon as you have stored what you need — the fastest way to protect somebody’s financial data is not to be holding it.

Irreversible, and it takes the data with it. After this call the id answers 404 exactly like one that never existed — not a deleted marker, not an empty result. Read the results first.

Status	Meaning
`204`	Gone. No body.
`404`	No such execution for your application, or it was already deleted.
`409`	It is still running. Only a closed execution can be deleted — stop it first, or wait for the `ended` event.

Executions you never delete are removed on their own after the platform’s retention period, but that is a safety net rather than a policy: data minimisation is yours to drive, and this is the call that drives it.

Server to server only. This call is authorised with your application secret: it belongs in your backend, never in a browser, a mobile app or anything your customer can read.

Delete an execution and everything retrieved under it. This is a purge, not an archive: the execution, its state, its records and its attachments are removed and cannot be recovered. **Call it as soon as you have stored what you need** — the fastest way to protect somebody's financial data is not to be holding it. <Warning> **Irreversible, and it takes the data with it.** After this call the id answers `404` exactly like one that never existed — not a *deleted* marker, not an empty result. Read [the results](api:GET/executions/results/{execution_id}/customer/v1/profile) first. </Warning> | Status | Meaning | | :--- | :--- | | `204` | Gone. No body. | | `404` | No such execution for your application, or it was already deleted. | | `409` | **It is still running.** Only a closed execution can be deleted — [stop it](api:DELETE/executions/handler/v1/{execution_id}/abort) first, or wait for the `ended` event. | Executions you never delete are removed on their own after the platform's retention period, but that is a safety net rather than a policy: data minimisation is yours to drive, and this is the call that drives it. <Note> **Server to server only.** This call is authorised with your application secret: it belongs in your backend, never in a browser, a mobile app or anything your customer can read. </Note>

Authentication

X-APP-SECRETstring

Application Secret

Path parameters

execution_idstringRequiredformat: "object-id"

The execution, as the acceptance response returned it.

Response

204 No Content
Gone — the execution, its state and the records it retrieved. From here on the id answers 404 exactly like one that never existed. No body.

Errors

404

Not Found Error

409

Conflict Error

422

Unprocessable Entity Error

Delete an execution and everything retrieved under it.

Irreversible, and it takes the data with it. After this call the id answers 404 exactly like one that never existed — not a deleted marker, not an empty result. Read the results first.

Status	Meaning
`204`	Gone. No body.
`404`	No such execution for your application, or it was already deleted.
`409`	It is still running. Only a closed execution can be deleted — stop it first, or wait for the `ended` event.

Server to server only. This call is authorised with your application secret: it belongs in your backend, never in a browser, a mobile app or anything your customer can read.