Skip to main content

Rate Limits

The VibePeak API implements rate limiting to ensure fair usage and maintain service quality for all users. Rate limits are based on your subscription plan.

Concurrent Task Limits

The primary rate limit is the number of concurrent video generation tasks you can have in progress at any time:
A task is considered “in progress” while it’s in queued or processing status. Once a task reaches completed or failed status, it no longer counts against your limit.

How It Works

When you submit a new slideshow request, the API checks your current number of in-progress tasks:
  1. If you’re under your limit, the task is accepted and queued
  2. If you’ve reached your limit, you receive a 429 Too Many Requests error

Rate Limit Response

When you exceed your concurrent task limit, you’ll receive:

Plan Required Response

If your account doesn’t have a qualifying plan (Plus, Pro, Max, or Enterprise):

Handling Rate Limits

Retrying with an Idempotency-Key

Responses to requests that carry an Idempotency-Key are stored and replayed for 24 hours, with one exception: a 429 or a 402 is never stored against the key. Both are refusals made before any credits are debited or any task is created, so nothing needs protecting. This means you can safely retry the same request with the same key after backing off (for a 429 CONCURRENCY_LIMIT_EXCEEDED) or after topping up credits (for a 402 INSUFFICIENT_CREDITS). The retry is evaluated again from scratch. Once it is accepted, that result is stored, and further retries with the same key replay it (with X-Idempotency-Replayed: true) without charging again. Every other response, including validation errors (400) and server errors (5xx), is stored and replayed as before. Reusing a key with a different payload returns 409 IDEMPOTENCY_CONFLICT.

Best Practices

Monitor Task Status

Track your in-progress tasks to avoid hitting limits

Use Webhooks

Get notified when tasks complete instead of polling

Queue Requests

Implement a local queue to manage submission rate

Handle 429 Gracefully

Implement exponential backoff for rate limit errors

Implementing a Task Queue

For high-volume applications, implement a local queue:

Upgrading Your Plan

Need higher limits? Upgrade your plan to increase your concurrent task quota:
  • Plus: 1 concurrent task
  • Pro: 3 concurrent tasks
  • Max: 5 concurrent tasks

Monitoring Usage

Keep track of your in-flight tasks to avoid rate limiting. The task status endpoint shows your active tasks.
You can monitor your usage by:
  1. Tracking the in_flight count in 429 error responses
  2. Maintaining a local counter of submitted vs completed tasks
  3. Using webhooks to get real-time completion notifications