UPCS Hourly Request Limit Explained

Every UPCS API key has an hourly request limit. By default it is 1,000 requests per hour. The limit protects the service and keeps one busy integration from using more than its allowance.

What counts

The limit belongs to the key. Everything that uses that key, whether it is a store plugin or your own server code, draws from the same allowance. That is why many teams use separate keys per site: a busy store cannot use up the allowance of a quiet one.

What happens at the limit

When a key reaches its limit, UPCS answers with HTTP 429 and a JSON error body shaped like this:

{
  "success": false,
  "message": "...",
  "code": "rate_limited"
}

The message wording can change, so rely on the HTTP status and the rate_limited code to identify the condition. Requests succeed again once the limit allows it.

What to do

1. Check the traffic. A map load on a busy checkout can add up. Look at how many map sessions and API calls your site makes per hour.
2. Avoid unnecessary calls. Do not call the API on every page view if you only need it at checkout; reuse results where you can.
3. Split keys. If two sites share one key, give each its own. See one key for every integration.
4. Handle 429 in code. Developers should detect rate_limited and back off. See handle the rate limit.

Do plugins show this?

If a plugin's connection test or map fails with a rate message, wait and try again. A rate_limited result does not mean the key is broken.

To discuss limits for your use case, use the contact page.