Too many requests without sufficient percentage of tokens authenticated.
429 errors
too_few_tokens_authenticated
429Too many requests
Error
{
"status_code": 429,
"request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
"error_type": "too_few_tokens_authenticated",
"error_message": "Too many requests without sufficient percentage of tokens authenticated.",
"error_url": "https://stytch.com/docs/b2b/api/errors/429#too_few_tokens_authenticated"
}too_many_requests
429Too many requests
Too many requests hit the Stytch API too quickly. We rate limit suspicious user activity per user, email, or phone number separately from global project rate limits.
Common causes
Activity from a suspicious user is causing you to send a large number of requests to the Stytch API in a short period of time.
A bug in your application or testing flow is causing you to unintentionally send a large number of requests to the Stytch API.
You are attempting to complete testing flows that require a large number of requests to be made for the same email address or phone number.
Troubleshooting steps
Implement an exponential backoff of your requests.
Investigate any suspicious user activity on your end and take appropriate action, such as blocking the offending user.
Check your codebase to make sure that you are not unintentionally sending more requests than necessary to the Stytch API.
Use our Test environment and sandbox values to complete testing flows.
Error
{
"status_code": 429,
"request_id": "request-id-test-b05c992f-ebdc-489d-a754-c7e70ba13141",
"error_type": "too_many_requests",
"error_message": "Too many requests have been made.",
"error_url": "https://stytch.com/docs/b2b/api/errors/429#too_many_requests"
}