← All features

Render destinations

Send finished files straight to S3, Drive, email, or a webhook.

Add a destination object to any render call and the output goes directly to Google Drive, an email address, a webhook URL, or hosted storage—no extra upload step.

Paid plans only — see plans

Nimo illustrating Render destinations

destination param on render endpoints

POST /api/v1/image
{
  "templateId": "tpl_123",
  "title": "Hello",
  "destination": { "type": "webhook", "url": "https://example.com/hook" }
}

→ { "requested": true,
     "delivery": { "type": "webhook", "ok": true } }

Four destination types

storage (hosted URL), webhook (signed payload), email, and Google Drive.

Signed webhook payloads

Webhook deliveries are signed with your API key’s stable webhook secret so receivers can verify authenticity.

Render never fails silently

A destination delivery failure doesn’t lose the render—you still get the file or a delivery.ok: false you can react to.

Build it once. Generate forever.

Create your free account