Skip to main content
Limits are counted per partner key and per endpoint group. Your partner key is the platform key you send in X-Api-Key. Calls in one group don’t use up another group’s limit. Partner API routes are counted by that key, not by IP address. The default window is 60 seconds.

Default limits

Each endpoint group covers one route. In production, a partner key with no custom limit uses the number below. A higher limit on your partner record replaces the default for that group only. The connect link needs no key, so it’s limited per visitor IP address: 120 requests / 60s. Past that it returns the same 429 body and Retry-After header.

When you exceed a limit

The API returns HTTP 429 with this error response:
Branch on error. Don’t parse message; the wording can change. The response also includes these headers: A successful response includes the three X-RateLimit-* headers and does not include Retry-After. Wait the number of seconds in Retry-After, then send the same request once. If that attempt is also 429, read Retry-After again and wait that long. The value is the time left in the current window, not a fixed full minute. If the header is missing or not a number, wait 60 seconds (one default window) before you retry.
Don’t retry immediately. Another call in the same window is rejected again.

Higher limits

A higher limit is stored on your partner record and applies without a client deploy. It changes that endpoint group only. Contact Branduo with the endpoint group and the rate you need.

Working within the limits

  • Request offers when you’re about to show them, not ahead of time. Each returned offer counts as a view.
  • Cache a merchant’s status rather than calling Get a brand on every page view. Use List brands with updatedSince to pick up changes.
  • Send a sync of up to 1,000 brands per Sync brands call instead of one brand per call.