WorkOS APIs are rate limited to ensure that they are fast for everyone. If you find yourself getting 429 errors, double check your integration to make sure you aren’t making unnecessary requests.
When a 429 Too Many Requests response includes a Retry-After header, wait for the indicated delay before retrying. Otherwise, retry with exponential backoff and a random delay; do not retry immediately or assume a fixed reset time.
| Name | Path | Limit |
|---|---|---|
| All requests | * | 6,000 requests per 60 seconds per API key |
This rate limit applies to all environments, staging and production. Exceptions to the general rate limit are listed below.
Authenticated API requests are counted per API key, not per source IP address. Spreading requests across multiple IP addresses does not increase your effective limit.
| Name | Path | Limit |
|---|---|---|
| Get Authorization URL | /sso/authorize | 1,000 requests per 60 seconds per connection |
| Name | Path | Limit |
|---|---|---|
| Directory Users | /directory_users | 4 requests per second per directory |
| SCIM provisioning | /scim/v2.0/* | 6,000 requests per 60 seconds per directory token |
| Name | Path | Limit |
|---|---|---|
| Delete Organization | /organizations/* | 50 requests per 60 seconds per API key |
| Name | Path | Limit |
|---|---|---|
| Create Event | /audit_logs/events | 9,000 requests per 60 seconds per API key |
Rate limiting for AuthKit APIs are enforced on a per environment basis.
| Name | Path | Limit |
|---|---|---|
| Reads | /user_management/* | 1,000 requests per 10 seconds |
| Writes | /user_management/* | 500 requests per 10 seconds |
| Authentication | /user_management/authenticate | 10 requests per 60 seconds per email or challenge ID |
| Magic Auth | /user_management/magic_auth/send | 3 requests per 60 seconds per email |
| Email verification | /user_management/:id/email_verification/send | 3 requests per 60 seconds per user |
| Password reset | /user_management/password_reset/send | 3 requests per 60 seconds per email |
Staging (sandbox) environments have a default invitation email quota of 100 per 24 hours, separate from the API request limits and Hosted AuthKit email sign-in limits. Send an invitation and Resend an invitation share this quota across the environment, not per recipient or API key.
The 24-hour window starts with the first counted attempt. The attempt that reaches 100 and subsequent attempts are blocked until the counter resets; this is not a guarantee of 100 delivered emails. Attempts can count even if no email is delivered. The quota applies to invitation emails sent by WorkOS, including through a custom email provider, but not when you disable WorkOS invitation emails and send them yourself.
When the quota is reached, the API returns 429 Too Many Requests with the message Sandbox environment email quota reached for invitation emails. Wait for the quota to reset before sending more invitations, or contact support if you need a higher sandbox quota.
Production environments with active billing are not subject to this sandbox quota. Production environments used before billing is set up have the same default invitation email quota. Other email sending safeguards still apply in production.
| Name | Limits |
|---|---|
| Reads | 1,000 requests per 10 seconds |
| Writes | 500 requests per 10 seconds |
| SSO sign-ins | 3 requests per 60 seconds per IP address |
| Email sign-ins | 10 requests per 60 seconds per email and IP address |
| Magic Auth sign-ins | 10 requests per 60 seconds per IP address and challenge ID |
| Magic Auth code requests | 3 requests per 60 seconds per IP address and email |
| Name | Path | Limit |
|---|---|---|
| Radar API | /radar/* (except /radar/signals) |
1,000 requests per 60 seconds per API key |
| Client signals | POST /radar/signals |
100 requests per 60 seconds per IP address |
| Send a Radar SMS challenge | POST /user_management/radar_challenges |
20 requests per 24 hours per IP address per environment |
The Radar API limit is shared across attempts and list operations and applies in addition to the general rate limit. Client signals use a separate limit.
The SMS challenge limit is shared across Hosted AuthKit and the User Management APIs. API requests use the ip_address parameter when provided, or the request’s IP address otherwise. Its 24-hour window starts with the first request, not at midnight. Additional per-phone-number sending and abuse-prevention limits also apply.
These request limits are separate from Radar’s risk-detection controls, which can block or challenge authentication attempts below these limits.
Magic Auth, email verification, password reset, and invitation emails sent through WorkOS’s default email provider are also subject to additional sending limits, on top of the request limits above, that protect deliverability for every customer on that shared infrastructure. These limits scale with an environment’s sending history and are tuned to respond to abuse patterns such as spam and phishing.
An environment on the default WorkOS email provider that sends an unusually high volume of email, or shows sending patterns associated with spam or phishing, may have some or all of its outbound email temporarily limited, independent of the request limits listed elsewhere on this page. This applies even when using a custom email domain: a custom domain gives control over that domain’s own authentication and reputation, but WorkOS still dispatches the mail through its shared default provider, so these limits still apply.
These shared-provider deliverability limits don’t apply to environments that connect a custom email provider. Sending through your own provider account takes WorkOS’s shared infrastructure out of the path – the most effective way to avoid these limits. It also gives full control over deliverability, and unlocks suppression management and complete delivery history. WorkOS’s other sending safeguards still apply to all outbound email, regardless of provider.
WorkOS also verifies that a recipient’s email domain can receive mail before sending Magic Auth codes and invitations. See testing with example domains for the recommended way to address test and placeholder users.