DELETE /v1/artifacts/{artifact_id} — Atom Files Developers

← API referenceFile intelligence · API access unavailable

API REFERENCE / FILE INTELLIGENCE

`DELETE` /v1/artifacts/{artifact_id}

Purge a derived output without deleting its source file.

Request fields

Location	Field	Type	Required	Description
Header	`Authorization`	string	Yes	Credential scoped to the authorized resource.
Path	`artifact_id`	string	Yes	Derived artifact to remove.
Header	`Idempotency-Key`	string	Yes	Stable retry identity.

Request example

Example request

DELETE /v1/artifacts/art_123
Authorization: Bearer <analysis-manage token>
Idempotency-Key: purge-artifact-8427

HTTP status codes

Status	Meaning
`202 Accepted`	Success response shown below.
`401 Unauthorized`	Missing, expired, or invalid credential.
`403 Forbidden`	Credential is valid but lacks the required scope or role.
`404 Not Found`	Artifact is absent or not visible to this caller.
`409 Conflict`	Artifact purge conflicts with another operation or retry identity.
`429 Too Many Requests`	Rate limit reached; honor Retry-After when provided.
`503 Service Unavailable`	Service temporarily unavailable; retry safely.

Response fields

Field	Type	Example
`operation_id`	string	op_602
`artifact_id`	string	art_123
`status`	string	purging
`source_version_id`	string	ver_012

Response example

Example response

202 Accepted
Content-Type: application/json

{
  "operation_id": "op_602",
  "artifact_id": "art_123",
  "status": "purging",
  "source_version_id": "ver_012"
}

How it works

New artifact reads and search results are denied immediately; byte and vector removal completes asynchronously and is confirmed by the operation receipt. Automatic regeneration of this artifact is suppressed for its source version until an explicitly authorized rerun. Dependent projections must be invalidated.