Requests are governed by account tier, per‑route permissions, and Redis‑backed rate limits. This guide explains tiers, defaults, and how to resolve 429 Too Many Requests.

​
Account tiers

Free

Base limits; good for evaluation and small workloads

Pro

Higher rate limits for growth and production pilots

Enterprise

Very high limits and custom SLAs

​
Base rate limits (per minute)

  • default: 10
  • search: 10
  • upload: 10
  • delete: 10

​
Permissions

  • API keys carry permissions such as view, create, update, delete
  • Admin levels: admin, super
  • Data scopes: read_public, read_private, write_public, write_private
If a route requires permissions you lack, calls may return 403 Unauthorized.

​
429 Too Many Requests

1

Identify the route

The details.api_name field indicates which bucket exceeded limits
2

Back off

Apply exponential backoff (e.g., 1s, 2s, 4s, jitter)
3

Reduce concurrency

Lower parallel calls to the route; batch where possible
4

Upgrade tier

Consider Pro/Enterprise for higher limits if usage is sustained

​
Best practices

Queue writes

Buffer high‑volume uploads to smooth bursts

Cache reads

Use application caching for hot reads to avoid duplicate calls

Batch operations

Prefer batch endpoints for objects and tasks where applicable

Monitor usage

Track 429s and latency; adjust client concurrency dynamically

​
See also