Request examples

Use a server-side Credential after setting up Images. The image ID below is synthetic: replace it with an image available to your account. Keep secrets in your environment or secret store.

Request image variants

curl --max-time 15 --include --request POST \
  'https://api.steamcall.com/v2/images/resolve' \
  --header "X-API-Key: $STEAMCALL_API_KEY" \
  --header 'Content-Type: application/json' \
  --header "Idempotency-Key: $STEAMCALL_IDEMPOTENCY_KEY" \
  --data '{"selector":{"type":"image_id","image_id":"img_11111111111111111111111111111111"},"sizes":[128],"formats":["webp","avif"]}'

Set a durable, nonempty idempotency key for this operation. Retain it when retrying an uncertain submission; do not reuse it for different input. This single request is not a polling loop and does not fetch delivery URLs.

Follow the response

For HTTP 202, respect Retry-After and GET the returned relative data.status_url on the same API origin with the same Credential. Use the exact status URL to preserve the requested variants. On an idempotency replay, follow the returned recovery link rather than submitting new work.

A polling response can return HTTP 200 while preparation continues. Inspect data.status and data.settled; stop when settled, and handle failed variants separately from ready ones. Use bounded delays with jitter and an application deadline. See resolve and polling for the complete response contract.

Prepare multiple images

Use the inline request in Batch preparation. Keep each input key unique, inspect each entry's outcome, and poll with the owning Service Account. One failed entry does not invalidate ready results.

Never copy the API Credential into frontend JavaScript. Send only returned ready delivery URLs to your frontend; see browser delivery for image markup.