Preview — pending review
This reference is generated from the platform API contract and is still under review. Operations, fields, and descriptions can change before publication.
Withdraw a transfer offer
Cancels an offer the donor project made. The volume is untouched and stays where it is; the
authKey that was handed out stops working the moment the offer is gone, which is the only
way to revoke a key that was shared with the wrong person.
Validation: unknown transferId → 404 NOT_FOUND. Caller needs owner|admin|contributor
on the scope that OWNS the offer (→ 403).
Async & state: Synchronous 204. Nothing about the volume changes, so nothing is
emitted.
Errors: 401; 403; 404; 500.
Idempotency/Concurrency: Idempotency-Key is optional (recommended); the replay returns
the original
204.
bearerTokenAuthorizationBearer <token>An API token (pc_live_…) or a service-account key (sak_live_…), created in Identity & Access Management and sent as Authorization: Bearer <token>. Requests are rate limited per credential and per tenant: every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset, and a refused request gets 429 RATE_LIMITED with Retry-After.
scopeId*stringOpaque ownership+authorization scope resolving to tenant + subscription + project.
transferId*stringIdentifier of the transfer offer to withdraw.
Idempotency-Key?stringOptional; recommended for safe retries. When sent, the same key+body within 24h replays the original result and the same key with a different body is 409 CONFLICT; keys are unique per tenant. When an API token or service-account (bearer) caller omits it, the request is applied once with no replay protection (a retry may apply it again). A console session gets one from the edge.
uuidOffer withdrawn.
curl -X DELETE "https://example.com/scopes/string/storage/volume-transfers/string"