One Click Videos · Developers
Rate limits and concurrency
Build a bounded queue and poll thoughtfully while your videos render.
The current public API does not publish a numerical requests-per-minute or concurrent-render quota. Do not assume unlimited throughput.
Practical client defaults
- Start with a small queue and one new video at a time until your workload is understood.
- Poll job status about every 15 seconds, with jitter when many jobs are active. This is suggested client behavior.
- Back off on transient GET errors. If a 429 response includes Retry-After, honor it.
- Keep a maximum polling duration and resume later with the same job ID.
- Do not retry a billable POST blindly after a timeout or connection loss.
Documented request bounds
| Resource | Bound |
|---|---|
| Video length | 5–300 seconds |
| Account API keys | Up to 10 |
| Reference images | Up to 12 per brief, 10 MB per image |
| Segment hints | Up to 10 |
| Styles list | Default 50; maximum 100 |
| Recent video list | Up to 25 |
Planning higher volume
Contact JEMSU support with your expected daily video count, durations and peak concurrency before scaling a large integration. No service-level or throughput commitment is stated on this page.