POST /v1/uploads/{operation_id}/transfer-plan

← API referenceWrite & track · API access unavailable

API REFERENCE / WRITE & TRACK

`POST` /v1/uploads/{operation_id}/transfer-plan

Refresh a short-lived transfer capability for the same upload operation.

Request fields

Location	Field	Type	Required	Description
Header	`Authorization`	string	Yes	Credential scoped to the authorized resource.
Path	`operation_id`	string	Yes	Existing upload operation; do not create a second file.

Request example

Example request

POST /v1/uploads/op_456/transfer-plan
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 is not visible.
`409 Conflict`	Operation cannot receive more bytes 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	ready_to_transfer
`transfer`	object	{…}
`transfer.method`	string	direct
`transfer.capability`	string	<short-lived, destination-scoped capability>
`transfer.expires_at`	string (date-time)	2026-10-20T18:10:00Z

Response example

Example response

200 OK
Content-Type: application/json

{
  "operation_id": "op_456",
  "status": "ready_to_transfer",
  "transfer": {
    "method": "direct",
    "capability": "<short-lived, destination-scoped capability>",
    "expires_at": "2026-10-20T18:10:00Z"
  }
}

How it works

Refreshing a plan must not create a second file. The data-plane protocol, acknowledged offsets, part sizes, capability binding, and resume semantics need integration tests before release.