Flikly Developers
Operations

Rate Limits

Developer API rate limits apply to every route under https://api.flikly.ai/api/v1/developer. Limits are separate from the main Flikly app and Clerk-authenticated routes.

Team and Custom plans

Only Team and Custom plans include Developer API access. Custom organizations use negotiated limits when configured; otherwise Team defaults apply.

Response headers

  • X-RateLimit-Limit — per-key minute limit
  • X-RateLimit-Remaining — per-key minute remaining
  • X-RateLimit-Reset — Unix timestamp, minute window reset
  • X-RateLimit-Limit-Organization-Day
  • X-RateLimit-Remaining-Organization-Day
  • X-RateLimit-Reset-Organization-Day
  • Retry-After — seconds (on HTTP 429)

HTTP 429 behavior

When exceeded, the API returns RATE_LIMIT_EXCEEDED with Retry-After. Back off and retry after the indicated interval. Inspect live usage via GET /usage/rate-limits or the portal Usage dashboard.

Concurrent job limits

Creating video or split jobs while at the concurrent cap returns CONCURRENT_JOB_LIMIT_EXCEEDED (also HTTP 429). Wait for active jobs to finish or poll unified jobs with status=processing.

Defaults (Team)

  • 60 requests per minute per API key
  • 10,000 requests per day per organization
  • 3 concurrent video jobs, 2 concurrent split jobs