Glossary

rate_limited

rate_limited is the 429 error OneLifeVibe returns when you go over your per-minute request limit. The response includes Retry-After and the limit headers.

Updated November 12, 2026

At OneLifeVibe

Related terms

What it means

rate_limited is an error code that travels with HTTP status 429. You get it when your requests to an API exceed the allowed number for the current minute. The request was not rejected because of a bad token or a server fault. It was rejected because the rate was too high, and the server wants you to slow down.

For OneLifeVibe, rate_limited is specifically the per-minute case. The response carries Retry-After, X-RateLimit-Limit and X-RateLimit-Remaining. Retry-After tells you how long to wait before sending again. The two X-RateLimit headers tell you the limit that applied and how many requests were left in that window. Treat the code as a signal to pause, not as a permanent failure.

How it works

Rate limiting counts requests over a time window. When the count crosses the limit, the server answers with 429 and stops processing that request. Retry-After gives a delay so your client knows when the window has room again. X-RateLimit-Limit is the ceiling for the window. X-RateLimit-Remaining is what was left when the response was built.

A good client reads Retry-After and waits at least that long. Then it retries with backoff and a cap, so a busy integration does not spin. It also checks X-RateLimit-Remaining during normal traffic. When the remaining count gets low, slow down before you hit rate_limited. That is cheaper than recovering from a 429.

Do not confuse a minute limit with a day quota. They use different codes at OneLifeVibe, and the fix is different. A minute limit clears when the window moves. A day quota needs a plan change or a prepaid call pack.

How OneLifeVibe uses it

OneLifeVibe returns 429 rate_limited when you go over the per-minute limit. The per-minute limits are Sandbox 10, Starter 60, Growth 300 and Scale 1,200. Over the limit, the response includes Retry-After, X-RateLimit-Limit and X-RateLimit-Remaining, so your client can wait and retry without guessing.

If you go over the day limit, the code is 429 quota_exceeded instead, unless a prepaid call pack has calls left. The packs are 25,000 calls for $9 a month and 250,000 calls for $49 a month, and you can cancel any time. Check the error code before you choose a response: rate_limited means wait for the minute window, quota_exceeded means the day allowance is the issue.

Common mistakes

The most common mistake is retrying a 429 immediately. That adds load and usually earns another rate_limited. Read Retry-After first, then retry after that delay.

Another mistake is treating rate_limited and quota_exceeded as the same thing. They are different codes with different causes. Retrying a quota_exceeded error on a short timer will not fix it. A prepaid call pack with calls left is the exception for the day limit.

Ignoring the X-RateLimit headers is also common. They come with the 429, so log them and use them to pace workers. Several workers sending in parallel can use the minute allowance faster than one worker, and a shared pause helps.

Questions

What is the difference between rate_limited and quota_exceeded?

rate_limited is the 429 for going over the per-minute limit and comes with Retry-After and the limit headers. quota_exceeded is the 429 for going over the day limit, unless a prepaid call pack has calls left.

How long should I wait after a 429 rate_limited?

Wait at least the delay in Retry-After, then retry. Use X-RateLimit-Remaining to slow down before the next request so you do not hit the same limit again.

See it working. The OneLifeVibe connector and Platform API put these pieces together.

Get a free key Read the docs

Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.