Why are requests restricted?
integration rate limits
You can set a minute-level or hour-level request limit for each integration to control burst traffic and protect access configurations. After the integration 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 integration.
Rate limiting takes effect separately for each integration. Please set appropriate caps for Web, iOS, and Android integrations based on actual traffic, and use independent integrations for test environments.
Impact of organizational status and quota
When the organization is deactivated, the package has expired, or the organization quota is exhausted, identification requests may not be processed normally. This differs from a single integration reaching its rate limit and usually requires an administrator to address the organization status, renew the plan, 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 integration. Don't rely solely on the HTTP status code to determine the cause.
Troubleshooting requests are limited
Please check in the following order:
- Confirm that the Public API Key used in the request belongs to the correct Region and integration.
- Check the minute-level and hour-level rate-limit configuration and current status in the integration details.
- Confirm whether the package has expired or the quota has been exhausted on the organization usage page.
- Record the Request ID, time and error code, and contact the support team for location.