Restaurant Brands Rate Limits

Restaurant Brands International's Partners API (Burger King's Partners API, served from rbictg.com) and Loyalty middleware are partner-scoped surfaces reached with credentials issued per environment, country, and brand. RBI's public developer documentation describes the request contract (bearer JWT for the Partners API; x-region, x-api-key, and x-user-datetime headers for the Loyalty middleware) but does not publish numeric request-rate, concurrency, or quota thresholds. Any throttling limits are governed by the bilateral partner agreement and the issued credential's scope, not a public per-key tier. Numbers below are recorded as descriptive strings and reconciled is false because RBI does not publish concrete figures.

Restaurant Brands Rate Limits is the machine-readable rate-limit profile for Restaurant Brands International on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring varies.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Rate Limiting, Partner Integration, and Quick Service Restaurants.

2 Limits Throttle: 429
Rate LimitingPartner IntegrationQuick Service Restaurants

Limits

Partners API requests (per partner credential) key
varies
not publicly documented; governed by partner agreement and JWT scope
Access is via an environment-, country-, and brand-scoped bearer JWT. RBI does not publish per-second or per-minute request ceilings.
Loyalty middleware requests (per API key) key
varies
not publicly documented; governed by partner agreement and x-api-key scope
Requests require x-region, x-api-key, and x-user-datetime headers. No public numeric rate ceiling is published.

Policies

Credential scoping
Limits are bound to the issued credential, which is specific to an environment (Staging/Production), country/region, vendor, and brand.
Bilateral governance
Concrete throttling thresholds are defined in the partner onboarding agreement with RBI rather than in public documentation.
Retry guidance
Treat 429 responses as throttling signals and apply exponential backoff; RBI does not publish a Retry-After contract publicly.

Sources