← 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
| Location | Field | Type | Required | Description |
|---|---|---|---|---|
| Header | Authorization | string | Yes | Credential scoped to the authorized resource. |
| Path | operation_id | string | Yes | Stable operation ID. |
Request example
Example request
GET /v1/operations/op_456
Authorization: Bearer <scoped token>HTTP status codes
| Status | Meaning |
|---|---|
200 OK | 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 | Operation does not exist or is not visible to this caller. |
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 |
|---|---|---|
id | string | op_456 |
kind | string (extensible) | file_upload Examples · extensible file_uploadmetadata_updateprocessing_policy_updateartifact_purge |
file_id | string | file_789 |
status | string | available |
updated_at | string (date-time) | 2026-10-20T18:00:00Z |
completion_receipt | object | {…} |
completion_receipt.kind | string | destination_commit |
completion_receipt.reference | string | <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 parameter
operation_idStable operation identifier.Expected fieldsKind, state, resource ID, last update, failure details if any, and a completion receipt when available.
Terminal states
available for a committed file, completed for policy or purge work, or failed, cancelled, or conflict.Polling interval, retention, and exact response schema remain unspecified.
