Restaurant Brands International
Restaurant Brands International (RBI, NYSE: QSR) is one of the world's largest quick service restaurant companies, with nearly $45 billion in annual system-wide sales and over 32,000 restaurants in more than 120 countries and territories. RBI operates four iconic brands — Tim Hortons, Burger King, Popeyes Louisiana Kitchen, and Firehouse Subs — and in May 2024 closed its $1B acquisition of Carrols Restaurant Group, Burger King's largest U.S. franchisee. RBI Tech Group (rbictg.com) publishes a partner developer portal (the RBI Developer Portal on Confluence) documenting the Partners API — a set of partner-onboarding REST APIs for third-party food ordering marketplaces and POS/kiosk vendors integrating into RBI's fulfillment platform. The documented surface includes ordering (price / commit / fire / place), menu and store retrieval, store-status and order/menu webhooks (Burger King's Partners API v1 "Channel" and v2 "Menu"), loyalty identification and transaction validation, and payment capture / refund endpoints. Access is bilateral: partners request a Staging environment and are issued environment-, country-, and brand-scoped credentials (a bearer JWT for the Partners API; x-region / x-api-key / x-user-datetime headers for the Loyalty middleware). There is no public self-service signup, pricing, or rate card. The public GitHub presence (github.com/rbilabs) is limited to internal tooling forks and an archived hackathon repo.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Restaurant Brands International the way a machine reads it — 303 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Restaurant Brands International scores 41.5/100 (developing), with a separate agent-readiness read of 35/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Restaurant Brands International's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/restaurant-brands/"
title="Restaurant Brands International on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/restaurant-brands.svg"
alt="Restaurant Brands International Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/restaurant-brands/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/restaurant-brands/"
title="Restaurant Brands International on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/restaurant-brands/card.svg"
alt="Restaurant Brands International Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Restaurant Brands International
Each block below is one kind of artifact we hold for Restaurant Brands International. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Restaurant Brands International Loyalty API
The Loyalty API from Restaurant Brands International — 1 operation(s) for loyalty.
Restaurant Brands International Menus API
The Menus API from Restaurant Brands International — 3 operation(s) for menus.
Restaurant Brands International Orders API
The Orders API from Restaurant Brands International — 5 operation(s) for orders.
Restaurant Brands International Stores API
The Stores API from Restaurant Brands International — 3 operation(s) for stores.
Open Collections 7
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONBurger King's Partners API
OPEN COLLECTIONBurger King's Partners API v2
OPEN COLLECTIONBurger King's Partners Loyalty API
OPEN COLLECTIONBurger King's Partners Loyalty Menus API
OPEN COLLECTIONBurger King's Partners Loyalty Orders API
OPEN COLLECTIONBurger King's Partners Loyalty Stores API
OPEN COLLECTIONScroll within the panel for all 7 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Restaurant Brands Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Restaurant Brands Finops
FINOPSSemantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 106
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Address
JSON SCHEMAAllergen
JSON SCHEMAAvailable
JSON SCHEMABalance
JSON SCHEMABrand
JSON SCHEMACalories
JSON SCHEMACartPriced
JSON SCHEMACart
JSON SCHEMACharges
JSON SCHEMACommitOrder
JSON SCHEMAConfigOfferEntry
JSON SCHEMACurrency
JSON SCHEMAcursor
JSON SCHEMACustomer
JSON SCHEMADateTime
JSON SCHEMADayPartId
JSON SCHEMADayPart
JSON SCHEMADiscount
JSON SCHEMADiscounts
JSON SCHEMAEntryId
JSON SCHEMAEntryRef
JSON SCHEMAEntry
JSON SCHEMAExternalReferenceId
JSON SCHEMAFee
JSON SCHEMAFeedback
JSON SCHEMAFeedbacks
JSON SCHEMAFees
JSON SCHEMAFireOrderInSeconds
JSON SCHEMAGeoPoint
JSON SCHEMAIdentifier
JSON SCHEMAIdentifierType
JSON SCHEMAIdentifyLoyalty
JSON SCHEMAIdentifyRequestDetails
JSON SCHEMAIdentifyRequest
JSON SCHEMAIdentifyResponse
JSON SCHEMAImage
JSON SCHEMAlimit
JSON SCHEMALocale
JSON SCHEMALocalizedText
JSON SCHEMALocation
JSON SCHEMALoyaltyBaseEntry
JSON SCHEMALoyaltyId
JSON SCHEMALoyalty
JSON SCHEMALoyaltyTransactionId
JSON SCHEMAMenu
JSON SCHEMAMenuSelectionPriced
JSON SCHEMAMenuSelection
JSON SCHEMAMFTaxes
JSON SCHEMAMoney
JSON SCHEMAMpfOrderId
JSON SCHEMANutrient
JSON SCHEMANutrition
JSON SCHEMAOperator
JSON SCHEMAOrderError
JSON SCHEMAOrderId
JSON SCHEMAOrderPlaced
JSON SCHEMAOrder
JSON SCHEMAOrderStatus
JSON SCHEMAPaymentMethod
JSON SCHEMAPayment
JSON SCHEMAPhone
JSON SCHEMAPlaceOrder
JSON SCHEMAPosVendor
JSON SCHEMAPOSOrderError
JSON SCHEMAPriceOrder
JSON SCHEMAPriceRange
JSON SCHEMAQuantityConstraints
JSON SCHEMAReadyInSeconds
JSON SCHEMAReason
JSON SCHEMARegion
JSON SCHEMARewardEntry
JSON SCHEMAServiceHour
JSON SCHEMAServiceMode
JSON SCHEMAStoreId
JSON SCHEMAStore
JSON SCHEMAStoreStatusChanged
JSON SCHEMAStoreStatus
JSON SCHEMASystemWideOfferEntry
JSON SCHEMATerminal
JSON SCHEMATimeSlot
JSON SCHEMATimezone
JSON SCHEMATransactionId
JSON SCHEMAWeekdayHours
JSON SCHEMAAllergen
JSON SCHEMAAvailability
JSON SCHEMACalories
JSON SCHEMAConfigOfferEntry
JSON SCHEMADayPartSchedule
JSON SCHEMADayPart
JSON SCHEMAEntryOptions
JSON SCHEMAEntryPrice
JSON SCHEMAImage
JSON SCHEMALocalizedString
JSON SCHEMALoyaltyEntry
JSON SCHEMAMenuEntry
JSON SCHEMAMenu
JSON SCHEMAMeta
JSON SCHEMANutrient
JSON SCHEMANutrition
JSON SCHEMAOption
JSON SCHEMAPaperCouponEntry
JSON SCHEMAQuantity
JSON SCHEMARewardEntry
JSON SCHEMAServiceMode
JSON SCHEMAStoreId
JSON SCHEMASystemWideOfferEntry
JSON SCHEMAScroll within the panel for all 106 ·
JSON Structure 106
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Channel Address Structure
JSON STRUCTUREChannel Allergen Structure
JSON STRUCTUREChannel Available Structure
JSON STRUCTUREChannel Balance Structure
JSON STRUCTUREChannel Brand Structure
JSON STRUCTUREChannel Calories Structure
JSON STRUCTUREChannel Cart Priced Structure
JSON STRUCTUREChannel Cart Structure
JSON STRUCTUREChannel Charges Structure
JSON STRUCTUREChannel Commit Order Structure
JSON STRUCTUREChannel Config Offer Entry Structure
JSON STRUCTUREChannel Currency Structure
JSON STRUCTUREChannel Cursor Structure
JSON STRUCTUREChannel Customer Structure
JSON STRUCTUREChannel Date Time Structure
JSON STRUCTUREChannel Day Part Id Structure
JSON STRUCTUREChannel Day Part Structure
JSON STRUCTUREChannel Discount Structure
JSON STRUCTUREChannel Discounts Structure
JSON STRUCTUREChannel Entry Id Structure
JSON STRUCTUREChannel Entry Ref Structure
JSON STRUCTUREChannel Entry Structure
JSON STRUCTUREChannel External Reference Id Structure
JSON STRUCTUREChannel Fee Structure
JSON STRUCTUREChannel Feedback Structure
JSON STRUCTUREChannel Feedbacks Structure
JSON STRUCTUREChannel Fees Structure
JSON STRUCTUREChannel Fire Order In Seconds Structure
JSON STRUCTUREChannel Geo Point Structure
JSON STRUCTUREChannel Identifier Structure
JSON STRUCTUREChannel Identifier Type Structure
JSON STRUCTUREChannel Identify Loyalty Structure
JSON STRUCTUREChannel Identify Request Details Structure
JSON STRUCTUREChannel Identify Request Structure
JSON STRUCTUREChannel Identify Response Structure
JSON STRUCTUREChannel Image Structure
JSON STRUCTUREChannel Limit Structure
JSON STRUCTUREChannel Locale Structure
JSON STRUCTUREChannel Localized Text Structure
JSON STRUCTUREChannel Location Structure
JSON STRUCTUREChannel Loyalty Base Entry Structure
JSON STRUCTUREChannel Loyalty Id Structure
JSON STRUCTUREChannel Loyalty Structure
JSON STRUCTUREChannel Loyalty Transaction Id Structure
JSON STRUCTUREChannel Menu Selection Priced Structure
JSON STRUCTUREChannel Menu Selection Structure
JSON STRUCTUREChannel Menu Structure
JSON STRUCTUREChannel Mftaxes Structure
JSON STRUCTUREChannel Money Structure
JSON STRUCTUREChannel Mpf Order Id Structure
JSON STRUCTUREChannel Nutrient Structure
JSON STRUCTUREChannel Nutrition Structure
JSON STRUCTUREChannel Operator Structure
JSON STRUCTUREChannel Order Error Structure
JSON STRUCTUREChannel Order Id Structure
JSON STRUCTUREChannel Order Placed Structure
JSON STRUCTUREChannel Order Status Structure
JSON STRUCTUREChannel Order Structure
JSON STRUCTUREChannel Payment Method Structure
JSON STRUCTUREChannel Payment Structure
JSON STRUCTUREChannel Phone Structure
JSON STRUCTUREChannel Place Order Structure
JSON STRUCTUREChannel Pos Vendor Structure
JSON STRUCTUREChannel Posorder Error Structure
JSON STRUCTUREChannel Price Order Structure
JSON STRUCTUREChannel Price Range Structure
JSON STRUCTUREChannel Quantity Constraints Structure
JSON STRUCTUREChannel Ready In Seconds Structure
JSON STRUCTUREChannel Reason Structure
JSON STRUCTUREChannel Region Structure
JSON STRUCTUREChannel Reward Entry Structure
JSON STRUCTUREChannel Service Hour Structure
JSON STRUCTUREChannel Service Mode Structure
JSON STRUCTUREChannel Store Id Structure
JSON STRUCTUREChannel Store Status Changed Structure
JSON STRUCTUREChannel Store Status Structure
JSON STRUCTUREChannel Store Structure
JSON STRUCTUREChannel System Wide Offer Entry Structure
JSON STRUCTUREChannel Terminal Structure
JSON STRUCTUREChannel Time Slot Structure
JSON STRUCTUREChannel Timezone Structure
JSON STRUCTUREChannel Transaction Id Structure
JSON STRUCTUREChannel Weekday Hours Structure
JSON STRUCTUREMenu V2 Allergen Structure
JSON STRUCTUREMenu V2 Availability Structure
JSON STRUCTUREMenu V2 Calories Structure
JSON STRUCTUREMenu V2 Config Offer Entry Structure
JSON STRUCTUREMenu V2 Day Part Schedule Structure
JSON STRUCTUREMenu V2 Day Part Structure
JSON STRUCTUREMenu V2 Entry Options Structure
JSON STRUCTUREMenu V2 Entry Price Structure
JSON STRUCTUREMenu V2 Image Structure
JSON STRUCTUREMenu V2 Localized String Structure
JSON STRUCTUREMenu V2 Loyalty Entry Structure
JSON STRUCTUREMenu V2 Menu Entry Structure
JSON STRUCTUREMenu V2 Menu Structure
JSON STRUCTUREMenu V2 Meta Structure
JSON STRUCTUREMenu V2 Nutrient Structure
JSON STRUCTUREMenu V2 Nutrition Structure
JSON STRUCTUREMenu V2 Option Structure
JSON STRUCTUREMenu V2 Paper Coupon Entry Structure
JSON STRUCTUREMenu V2 Quantity Structure
JSON STRUCTUREMenu V2 Reward Entry Structure
JSON STRUCTUREMenu V2 Service Mode Structure
JSON STRUCTUREMenu V2 Store Id Structure
JSON STRUCTUREMenu V2 System Wide Offer Entry Structure
JSON STRUCTUREScroll within the panel for all 106 ·
Examples 70
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Channel Address Example
EXAMPLEChannel Allergen Example
EXAMPLEChannel Available Example
EXAMPLEChannel Balance Example
EXAMPLEChannel Calories Example
EXAMPLEChannel Cart Example
EXAMPLEChannel Cart Priced Example
EXAMPLEChannel Charges Example
EXAMPLEChannel Commit Order Example
EXAMPLEChannel Customer Example
EXAMPLEChannel Day Part Example
EXAMPLEChannel Discount Example
EXAMPLEChannel Entry Example
EXAMPLEChannel Entry Ref Example
EXAMPLEChannel Fee Example
EXAMPLEChannel Feedback Example
EXAMPLEChannel Geo Point Example
EXAMPLEChannel Image Example
EXAMPLEChannel Location Example
EXAMPLEChannel Loyalty Example
EXAMPLEChannel Menu Example
EXAMPLEChannel Mftaxes Example
EXAMPLEChannel Money Example
EXAMPLEChannel Nutrient Example
EXAMPLEChannel Nutrition Example
EXAMPLEChannel Order Error Example
EXAMPLEChannel Order Example
EXAMPLEChannel Order Placed Example
EXAMPLEChannel Payment Example
EXAMPLEChannel Place Order Example
EXAMPLEChannel Price Order Example
EXAMPLEChannel Price Range Example
EXAMPLEChannel Reward Entry Example
EXAMPLEChannel Service Hour Example
EXAMPLEChannel Store Example
EXAMPLEChannel Time Slot Example
EXAMPLEMenu V2 Allergen Example
EXAMPLEMenu V2 Availability Example
EXAMPLEMenu V2 Calories Example
EXAMPLEMenu V2 Day Part Example
EXAMPLEMenu V2 Entry Price Example
EXAMPLEMenu V2 Image Example
EXAMPLEMenu V2 Menu Entry Example
EXAMPLEMenu V2 Menu Example
EXAMPLEMenu V2 Meta Example
EXAMPLEMenu V2 Nutrient Example
EXAMPLEMenu V2 Nutrition Example
EXAMPLEMenu V2 Option Example
EXAMPLEMenu V2 Quantity Example
EXAMPLEMenu V2 Reward Entry Example
EXAMPLEScroll within the panel for all 70 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Restaurant Brands International — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 8
Properties that don't map to a standard resource type
Scroll within the panel for all 8 ·
← All providers · Data indexed from github.com/api-evangelist/restaurant-brands · machine-readable index on apis.io
This is an independent, third-party profile of Restaurant Brands International, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.