/developers
Developer docsAtom Files ↗
← API referenceWrite & track · API access unavailable
API REFERENCE / OPERATIONS

GET /v1/operations/{operation_id}

Read the durable state of an accepted file operation. This is the recovery point after a timeout, lost acknowledgement, or offline destination.

Request fields

LocationFieldTypeRequiredDescription
HeaderAuthorizationstringYesCredential scoped to the authorized resource.
Pathoperation_idstringYesStable operation ID.

Request example

Example request
GET /v1/operations/op_456
Authorization: Bearer <scoped token>

HTTP status codes

StatusMeaning
200 OKSuccess response shown below.
401 UnauthorizedMissing, expired, or invalid credential.
403 ForbiddenCredential is valid but lacks the required scope or role.
404 Not FoundOperation does not exist or is not visible to this caller.
429 Too Many RequestsRate limit reached; honor Retry-After when provided.
503 Service UnavailableService temporarily unavailable; retry safely.

Response fields

FieldTypeExample
idstringop_456
kindstring (extensible)file_upload
Examples · extensiblefile_uploadmetadata_updateprocessing_policy_updateartifact_purge
file_idstringfile_789
statusstringavailable
updated_atstring (date-time)2026-10-20T18:00:00Z
completion_receiptobject{…}
completion_receipt.kindstringdestination_commit
completion_receipt.referencestring<receipt reference>

Response example

Example response
200 OK
Content-Type: application/json

{
  "id": "op_456",
  "kind": "file_upload",
  "file_id": "file_789",
  "status": "available",
  "updated_at": "2026-10-20T18:00:00Z",
  "completion_receipt": {
    "kind": "destination_commit",
    "reference": "<receipt reference>"
  }
}

How it works

Path parameteroperation_idStable operation identifier.
Expected fieldsKind, state, resource ID, last update, failure details if any, and a completion receipt when available.
Terminal statesavailable for a committed file, completed for policy or purge work, or failed, cancelled, or conflict.

Polling interval, retention, and exact response schema remain unspecified.