← API referenceWrite & track · API access unavailable
API REFERENCE / UPLOADS
POST /v1/uploads/{operation_id}/finish
The sender says it has finished the assigned transfer. Atom moves the operation into destination verification; this call alone never asserts that the file is available.
Request fields
| Location | Field | Type | Required | Description |
|---|---|---|---|---|
| Header | Authorization | string | Yes | Credential scoped to the authorized resource. |
| Path | operation_id | string | Yes | Operation returned by create upload. |
Request example
Example request
POST /v1/uploads/op_456/finish
Authorization: Bearer <scoped token>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 | Operation does not exist or is not visible to this caller. |
409 Conflict | Operation cannot be finished in its current state. |
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_456 |
status | string | verifying |
Response example
Example response
202 Accepted
Content-Type: application/json
{
"operation_id": "op_456",
"status": "verifying"
}How it works
Path parameter
operation_idThe ID returned by POST /v1/uploads.Retry behaviorRepeating
finish for the same operation must be safe. Inspect operation status after an ambiguous response.Success meaningTransfer report accepted; wait for a destination receipt before treating the file as available.
Request shape, HTTP status codes, and receipt format remain unspecified.