Rendergrid API

Rendergrid is a wholesale image-generation API. You authenticate with an API key, send a generation request, and get the result back asynchronously — generation requests return 202 Accepted immediately with a creation id, which you poll (or receive a webhook for) until it completes. All requests and responses are JSON, except file uploads which use multipart form data.

Base URL

https://api.rendergrid.io/api/public/v1

All paths in these docs are relative to the base URL. Traffic is HTTPS-only.

Quickstart

1. Get an API key

Create a key in the client portal. Production keys look like rg_live_xxx. Send the key on every request in the Authorization: Bearer header — see Authentication for details and key-handling advice.

2. Generate your first image

curl -X POST https://api.rendergrid.io/api/public/v1/images/generate \
  -H "Authorization: Bearer rg_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "nano-banana-2",
    "prompt": "a studio product shot of a ceramic mug on a marble surface",
    "aspect_ratio": "1:1"
  }'

The request is accepted immediately with 202 and your wallet is charged the shown cost up front (refunded in full if generation fails):

202 Accepted
{
  "id": "5b0214ae-9e39-460a-820a-f6ae3e24400b",
  "status": "queued",
  "task_id": "5b0214ae-9e39-460a-820a-f6ae3e24400b",
  "cost": 0.1
}

3. Poll for the result

poll.sh
curl https://api.rendergrid.io/api/public/v1/creations/5b0214ae-9e39-460a-820a-f6ae3e24400b \
  -H "Authorization: Bearer rg_live_xxx"

Poll at most once every 5 seconds per creation — faster polling returns 429. Status moves queued processing completed or failed. When completed, the response carries the output URLs:

200 OK
{
  "id": "c0ea4d5b-c965-4943-aaad-76fda0c53ca9",
  "status": "completed",
  "result_urls": [
    "https://cdn.rendergrid.io/images/2026/07/02/…/8b5f7dcb_…_req_c0ea4d5b.jpg"
  ]
}

Prefer callbacks over polling? Pass a webhook_url in the generation request and we POST you a signed event when the creation finishes — see Webhooks.

Next steps

  • Generate image — the full request schema: aspect ratios, resolution tiers, reference images, batching.
  • Models — the model catalog and per-image pricing for your account.
  • Job status — creation statuses, response fields, and polling rules.
  • Webhooks — signed callbacks on completion, with verification code samples.
  • Errors — the error envelope and the full error-code table.
  • Idempotency — retry requests safely without double charges.
  • Rate limits — per-key limits, concurrency, and how to back off.