Why are requests restricted?

endpoint rate limits

You can set a minute-level or hour-level request limit for each endpoint to control burst traffic and protect access configurations. After the endpoint reaches the upper limit, new requests will return a rate-limit error; after the rate-limit window is restored, the request will naturally resume without re-creating the endpoint.

rate limiting takes effect separately based on the endpoints. Please set appropriate caps for web, iOS, and Android endpoints based on actual traffic, and use independent endpoints for test environments.

Impact of organizational status and quota

When the organization is deactivated, the package has expired, or the organization quota is exhausted, the identification request may not be processed normally. This kind of situation is different from a single endpoints reaching the rate limit, which usually requires the administrator to handle the organization status, renew or adjust the quota.

If multiple conditions occur at the same time, please first check the error code returned by the interface and the console organization status, and then check the rate-limit configuration of the endpoint. Don't rely solely on the HTTP status code to determine the cause.

Troubleshooting requests are limited

Please check in the following order:

1. Confirm that the Public API Key used in the request belongs to the correct Region and endpoint.
2. Check the minute-level and hour-level rate-limit configuration and current status in the endpoint details.
3. Confirm whether the package has expired or the quota has been exhausted on the organization usage page.
4. Record the Request ID, time and error code, and contact the support team for location.