Rate limit
Nedir Rate limit?
Bu terim şu anda yalnızca İngilizce olarak sunulmaktadır.
A rate limit caps how many API requests you may send in a given window — the default is a per-second burst threshold separate from the per-minute rate limit, and higher org tiers raise the ceiling. When your traffic exceeds the limit, Orbit returns an HTTP 429 envelope naming the limit you broke and the reset timing to wait before retrying.
More detail
Rate limits guard both the API surface and the messaging/voice throughput downstream — the platform rejects excess requests at the edge so a burst from one tenant doesn't degrade another's sends. Message sends also carry a separate per-service cap (messaging services, sender pools) that throttles you at the messaging layer rather than the API edge.
The reliable client pattern is to parse the 429 envelope (retry-after-style JSON), honor its timing instead of spinning on tight retries, and scale down campaign pacing — especially on timed-out tests, which often breed the exact bursts that trip the limit.
Sık sorulan sorular
- What status code does Orbit return over the rate limit?
- HTTP 429. The response envelope names which limit fired and how long to wait before retrying — treat it as a deterministic pause, not a cause to hammer the endpoint again.
- Is a messaging-service MPS cap the same thing as a rate limit?
- It's a specific kind of rate limit: the API-edge 429 is burst-driven per-second/per-minute, while a messaging service's MPS cap throttles outbound sends at the message layer and surfaces as a service-level exceeded error rather than an HTTP 429.
See also
Build it on Orbit
Voice, messaging, email, video, and AI agents on one platform and one pay-as-you-go bill. Start free — no credit card required.