Rate Limits
The Developer API enforces rate limits to ensure fair usage and system stability.
When rate limits are exceeded, you’ll receive a
429 Too Many Requests response:
Credit Costs
Each API operation consumes credits from your organization’s balance.TTLs (Time-To-Live)
Cleanup Schedule
The API runs automatic cleanup to remove expired resources:- Expired temporary images are deleted from storage (every 60 minutes)
- Completed render jobs older than 1 hour are removed (every 60 minutes)
- Expired tool files and completed tool jobs are removed (every 10 minutes)
- Associated files are permanently deleted
Concurrent Job Limits
The maximum number of concurrent render jobs depends on your subscription plan:
Buying a permanent top-up unlocks Developer API access on Engine and Editor, but does not raise their five-job concurrency tier.
This limit includes:
- Single render jobs (each counts as 1)
- Bulk render jobs (each counts as 1, regardless of item count)
Best Practices
Implement exponential backoff
Implement exponential backoff
When you receive a
429 response, wait before retrying. Start with 1 second and double the wait time for each subsequent retry, up to a maximum of 60 seconds.Download files promptly
Download files promptly
Download completed renders immediately after job completion. The 1-hour TTL is a hard limit — files are permanently deleted after expiration.
Monitor your credit balance
Monitor your credit balance
Check your credit balance before submitting large bulk jobs. Use the billing endpoints to verify sufficient credits are available.
Use webhooks for bulk jobs
Use webhooks for bulk jobs
Instead of polling, provide a
webhookUrl when creating bulk jobs to receive instant completion notifications.Batch efficiently
Batch efficiently
For bulk renders, group up to 100 items per job to minimize API calls while staying within limits.