Skip to main content
POST
Complete an owned image reference upload using the part numbers and ETags from PUT requests. Verifies the stored file size. Use the returned fileKey as the generation reference.

Authentication and permissions

string
required
Send a VoiceCheap API key in this header. Authorization: Bearer with the same API key is also supported. OAuth access tokens are accepted only by MCP, not by this REST endpoint.
Required permissions: images:write. An active paid subscription is required. Permissions do not change team roles, resource ownership, media credits, or plan limits.

Parameters

string
Optional at the transport boundary: the server injects an identifier before validation when omitted. Supply your own stable UUID v4 to recover safely from a lost response.Format: “uuid”. Pattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-4[0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$.
string
required
The uploadId returned by this domain’s upload_initialize action.Format: “uuid”. Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$.
array
required
List of values. See the complete input schema for its item structure.Minimum items: 1. Maximum items: 2.
The JSON Schema below preserves the exact field names, nested types, defaults, bounds, and accepted values exposed by discovery. Additional cross-field rules are listed in the operation notes.

Idempotency

Use a UUID v4 in requestId or the Idempotency-Key HTTP header for each mutation. Reuse the same identifier and identical arguments after a network failure. If both are supplied, they must match. Replaying a saved request does not repeat the operation or charge another monthly call. Failed or interrupted requests are not restarted automatically. Every mutation can return HTTP 202 when a retry finds the same request still running, even when its first execution is normally synchronous. If execution completed but resultStored is false, a retry returns HTTP 200 with saved request state instead of the original result. Retrieve the output through its domain history, result, or download action.

Request examples

Replace example resource identifiers and media keys with values returned for your account. Keep the request identifier stable when retrying the same mutation.

Response

A successful first execution returns HTTP 200 with the operation result under data. A replay may return saved request state instead. The example shows one supported response, not every optional field. The completed owned reference key and its read URL, returned only after the stored byte length exactly matches the declared file size. Use fileKey, not readUrl, in generation arguments.

Result fields

Recover and poll this request

Use the same identifier even after a lost connection. If resultStored is false, retrieve the output through the corresponding history, result, or download action. Never start a second generation merely to check progress.
HTTP 200

Operation notes

  • Requires images:write; no additional upload scope is needed.
  • uploadId is the UUID from initialize. parts contains exactly the 1–2 parts required by the session. Each part has an integer partNumber from 1 to 2 and an etag string of 1–256 characters taken from its successful PUT response.
  • All part numbers must be present and unique. Parts are sorted before completion; ETags are normalized to quoted values. You may preserve the ETag quotes returned by storage.
  • The completed object’s actual byte length is checked against fileSize and the 8 MiB cap. A missing, mismatched, or oversized length causes the object and active session to be removed and returns UPLOAD_SIZE_MISMATCH.
  • Pass fileKey as referenceImageKey in images_generate. Completed reference files can be reused for subsequent image or thumbnail generations owned by the same user; generation does not consume the reference.
  • Only an upload belonging to the connected user can be signed, completed, or aborted. These aliases accept only JPG, PNG, and WebP sessions of at most 8 MiB, even if the session was created through a different upload family.
  • The production upload session expires after 24 hours. Signed part URLs expire after one hour. Completion and abort remove the active session; sign-parts and complete then return Upload not found. Neither response includes an expiresAt field.
  • Use a UUID v4 requestId, or the HTTP Idempotency-Key header, and reuse it with identical inputs when retrying. The integration layer records each mutation and returns its recorded state or result without rerunning it. A failed or interrupted request is not automatically retried.
  • Completion closes the multipart session. Retry completion with the original requestId to retrieve its recorded result; a new completion request for that closed uploadId returns Upload not found. No reference-retention expiry is returned by this action.

Usage

Each successful invocation consumes one monthly API/MCP call. Media credits and the operation’s own generation allowances also apply.

Errors