Batch preparation

POST /v2/images/resolve-batch with 1–100 uniquely keyed entries:

{
  "items": [
    {
      "key": "thumbnail",
      "request": {
        "selector": {
          "type": "image_id",
          "image_id": "img_11111111111111111111111111111111"
        },
        "sizes": [128],
        "formats": ["webp", "avif"]
      }
    }
  ]
}

The image ID is synthetic. HTTP 200 acknowledges the durable batch, not completion. Results preserve input order; inspect each status_code and state. A pending entry has no fabricated image ID. A refused entry does not discard accepted work in other entries.

Poll the returned data.status_url using the owning Service Account. The batch settles when every entry has an outcome and every accepted variant has settled. Another Service Account cannot recover it, even within the same Customer. Credential rotation within the owning Service Account preserves identity.

Reuse one idempotency key for uncertain submission retries, then recover with the returned status link. A conflicting body must use a new intentional operation. Bound both polling time and submission concurrency; a 100-entry batch is not permission to run unlimited batches.