Glossary
quota_exceeded
The 429 error OneLifeVibe returns when your daily API calls are used up. Retry-After counts the seconds to the 00:00 UTC reset.
Updated November 12, 2026
At OneLifeVibe
- Over the minute limit: 429 rate_limited with Retry-After, X-RateLimit-Limit and X-RateLimit-Remaining. Over the day: 429 quota_exceeded, unless a prepaid call pack (25,000 calls for $9 a month, 250,000 for $49 a month, cancel any time) has calls left.
- Daily calls: Sandbox 1,000, Starter 5,000, Growth 100,000, Scale 1,000,000 (annual plans 25% more). Over it: 429 quota_exceeded with Retry-After counting to 00:00 UTC, unless a call pack has calls left (25,000 for $9 a month or 250,000 for $49 a month, cancel any time).
Related terms
What it means
quota_exceeded is an error code returned with HTTP status 429, Too Many Requests. It means you have used the calls your plan allows for the current day, so the server refuses more until the daily counter resets, unless a call pack has calls left.
A bare 429 tells you a request was throttled, not why. OneLifeVibe puts a short error code in the response body to separate the cases: rate_limited for a burst over the per-minute limit, quota_exceeded for the daily allowance. Read the code before you decide what to do, because the wait is different.
The response carries a Retry-After header. For quota_exceeded it holds the seconds until midnight UTC, when the daily count starts again. That can be hours, so treat it as a scheduling instruction, not a cue to retry in a loop.
How it works
Rate limits and quotas both produce 429s, so the status alone will not tell them apart. A rate limit caps how fast you call; a quota caps how much you call in a period. OneLifeVibe enforces both: a per-minute limit that returns rate_limited, and a daily call allowance that returns quota_exceeded.
When the daily allowance is gone, OneLifeVibe checks for a prepaid call pack with calls left. If one exists, the request is served. If not, you get 429 quota_exceeded with Retry-After counting to 00:00 UTC.
Either way, back off, log the error code and the Retry-After value, and resume when the header says so. Branch your retry logic on the code string, not on the status alone.
How OneLifeVibe uses it
Daily calls by plan: Sandbox 1,000, Starter 5,000, Growth 100,000, Scale 1,000,000. Annual plans include 25% more. When a plan's daily calls are used, the next request returns 429 quota_exceeded with Retry-After counting to 00:00 UTC, unless a prepaid call pack has calls left.
Call packs: 25,000 calls for $9 a month, or 250,000 calls for $49 a month, cancel any time.
A burst over the per-minute limit is a separate event. It returns 429 rate_limited with Retry-After, X-RateLimit-Limit and X-RateLimit-Remaining. Use those headers to pace requests within the minute limit, before you reach the daily ceiling.
Common mistakes
The usual mistake is treating every 429 as quota_exceeded. Over the minute limit you get rate_limited instead. Check the body.
Ignoring Retry-After is the next one. Sleeping a fixed 60 seconds on a daily quota can mean a day of pointless retries. Parse the header and schedule the work.
Do not assume the reset comes 24 hours after your first call. It comes at 00:00 UTC for everyone, which matters if you run batch jobs near the end of the day.
Questions
What is the difference between rate_limited and quota_exceeded?
Both arrive as 429 responses. rate_limited means you went over the per-minute limit; quota_exceeded means you used the daily calls your plan allows. Retry-After is short for the first and counts to 00:00 UTC for the second.
When does the OneLifeVibe daily quota reset?
At 00:00 UTC. The Retry-After header on quota_exceeded gives the number of seconds until that reset, so you do not have to calculate it.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.