Skip to main content
POST
Prepare a JPG, PNG or WebP reference upload up to 8 MiB. Use thumbnails_upload_sign_parts to get PUT URLs, upload the bytes, then call thumbnails_upload_complete and use its fileKey when generating.

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: thumbnails: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 image filename, with an extension matching contentType.Minimum length: 1. Maximum length: 250. Pattern: \.(?:jpe?g|png|webp)$.
string
required
Text value.Allowed values: “image/jpeg”, “image/png”, “image/webp”.
integer
required
Exact file size in bytes, up to 8 MiB.Minimum: 1. Maximum: 8388608.
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. A new multipart image-reference upload session, the future object key, the part size in bytes, and the maximum parallel-upload count. This does not upload any image bytes or make key ready for generation.

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 thumbnails:write; no additional upload scope is needed.
  • filename is trimmed, must contain 1–250 characters, and must end in .jpg, .jpeg, .png, or .webp. Its extension must match contentType: image/jpeg, image/png, or image/webp. fileSize is the exact integer byte count, from 1 to 8,388,608.
  • The shared upload implementation returns partSize 5 MiB (5,242,880 bytes) for these references. A file of at most 5 MiB uses one part; a larger file up to 8 MiB uses two. Request PUT URLs with thumbnails_upload_sign_parts, upload the bytes, then call thumbnails_upload_complete.
  • Use the fileKey returned by completion as an entry in referenceImageKeys in thumbnails_generate. The initialize result uses key, not fileKey. Do not pass key to generation before completion.
  • 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.
  • This action uses the connected user’s own creations and uploads, including when the credential is connected in a team context.
  • 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.
  • The filename in the object key is sanitized and may be shortened. Keep the exact returned key and uploadId; do not construct them yourself. Image bytes are validated during generation as well as the declared size and type during upload.

Usage

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

Errors