Last updated · May 2026
- Production-ready APIs
- SOC 2 Type I - In Progress
RATE_LIMIT_EXCEEDED
HTTP 429 with next_step=wait. Your key has exceeded its sliding-window per-minute limit.
What it means
DataVibe enforces sliding-window rate limits per API key tier. The full set lives in SLO_AND_SCALE.md §4.2: starter 300/min, pro 600/min, enterprise 2000/min, and a stricter 40/min lane for past-due subscriptions.
How to fix
- Read
retry_after_secondsin the JSON body and wait that long before retrying. The same value lands in theRetry-Afterheader. - Read
X-RateLimit-Remainingon every response so you can throttle proactively before getting 429s. - If you consistently hit the limit, upgrade your plan or contact support to discuss a higher tier.
Curl repro
curl -i https://api.datavibe.cc/v1/extract \
-H "Authorization: Bearer dv_live_..." \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com"}'