Async Rendering and Webhooks

For long-running renders (videos, complex templates), use async mode to avoid timeouts.

When to Use Async

• Video (MP4) rendering
• Large/complex templates
• Batch operations
• When you don't need immediate response

Enabling Async Mode

{
  "template": "TEMPLATE_ID",
  "format": "mp4",
  "duration": 30000,
  "async": true,
  "webhook_url": "https://your-server.com/webhook"
}

Response

Async requests return immediately with a job reference:

{
  "id": "render-uuid",
  "status": "processing",
  "message": "Render is being processed"
}

Webhook Notification

When rendering completes, we POST to your webhook_url:

{
  "success": true,
  "render_id": "render-uuid",
  "status": "COMPLETED",
  "url": "https://templated-assets.s3.amazonaws.com/..."
}

Polling Alternative

If you can't receive webhooks, poll the render status:

curl https://api.templated.io/v1/renders/RENDER_ID \
  -H "Authorization: Bearer YOUR_API_KEY"

Response includes status: processing, completed, or failed.

Error Handling

If a render fails, the webhook payload indicates failure:

{
  "success": false,
  "render_id": "render-uuid",
  "status": "FAILED",
  "error": "Error message"
}

Best Practices

1. Always use async for video renders
2. Implement webhook endpoint for production
3. Store render IDs to track status
4. Set reasonable timeouts in your application
5. Handle failures gracefully

Updated on: 11/01/2026