# Brinker International

> Brinker International (NYSE: EAT) is a Dallas, Texas casual-dining restaurant company
> that owns, operates and franchises Chili's Grill & Bar and Maggiano's Little Italy.
> It runs a real API program on Google Apigee — a gateway at api.brinker.com and an
> Apigee Integrated Developer Portal at developer.brinker.com — but that program is
> entirely partner- and franchise-facing. There is no public, self-service developer
> API, no published OpenAPI or other machine-readable contract, no SDK, no MCP server,
> no agent card and no open GitHub organization. This file is GENERATED by the API
> Evangelist enrichment pipeline from the profile in apis.yml and from live probes of
> Brinker's own hosts; it is not published by Brinker.

generated: 2026-09-04
method: generated
source: apis.yml + live probes of brinker.com, chilis.com, maggianos.com, api.brinker.com, developer.brinker.com

## What is callable

Nothing, anonymously. Brinker publishes zero machine-readable contracts.

- api.brinker.com is a live Apigee Edge gateway (CNAME brinker-prod.apigee.net). Every
  probed path returns HTTP 404 with the Apigee fault
  "Unable to identify proxy for host: secure and url: /"
  (errorcode messaging.adaptors.http.flow.ApplicationNotFound). The gateway is running;
  no anonymously routable proxy is published on it.
- developer.brinker.com is a Google Apigee Integrated Developer Portal (site id
  "brinker-portal"). Its API catalog endpoint
  /portals/api/sites/brinker-portal/apidocs returns HTTP 401
  ("No authorization header provided"). Its anonymous catalog endpoint
  /portals/api/sites/brinker-portal/liveportal/apis returns HTTP 200 with
  apiDocs: [], apiProducts: [], apiCategoryList: [] — nothing published to the public.
- The QA portal at developerqa.brinker.com (site id "brinkerqa-portal") returns the
  same empty apiDocs/apiProducts anonymously but names six API product categories:
  LoyaltyEA, Promos, ITSM ServiceNow, GMS, OrderManagement, POS. These are category
  labels only. No path, operation, schema or base URL is exposed.

## How access works

Access is approval-gated and entitlement-based, per Brinker's own portal FAQ:

1. Create an account at https://developer.brinker.com/accounts/create
2. Account is created PENDING APPROVAL by the "Brinker API Team"
3. After approval, sign in and create a developer app requesting Default Product access
4. Brinker assigns the API Product from the backend based on your entitlement
5. Brinker activates the credentials; Apigee consumer key and secret then become visible

There is no OAuth authorization server, no OpenID Connect discovery document and no
published scope reference on any Brinker host.

## Websites

- Brinker International: https://www.brinker.com
- Chili's Grill & Bar: https://www.chilis.com
- Maggiano's Little Italy: https://www.maggianos.com
- Investor Relations: https://investors.brinker.com
- Domestic Franchising: https://brinker.com/franchise/domestic
- Franchise Partner Portal (login): https://franchise.brinker.com
- Privacy: https://brinker.com/privacy
- Terms and Conditions: https://brinker.com/terms-and-conditions

## Developer surfaces

- Partner API Developer Portal (SSO/approval gated): https://developer.brinker.com
- Developer Portal FAQs (public): https://developer.brinker.com/faqs
- Developer account registration: https://developer.brinker.com/accounts/create

## Vendor-operated surfaces (NOT Brinker-authored APIs)

These are real HTTP APIs that serve Brinker properties, but they are vendor platforms
running under a Brinker tenant. They are recorded for accuracy and are deliberately NOT
registered as Brinker APIs, because the contract, operations and semantics belong to the
vendor, not to Brinker.

- Prismic Content API v2 (brinker.com CMS): https://brinker-production.cdn.prismic.io/api/v2
- Prismic Content API v2 (maggianos.com CMS): https://maggianos-prod.cdn.prismic.io/api/v2
- Olo-powered online ordering: https://orders.maggianos.com
- Nutritionix-hosted nutrition data for Chili's: https://restaurant.nutritionix.com

## Artifacts in this profile

- security/brinker-international-domain-security.yml — probed TLS/HSTS/DNSSEC/CAA/SPF/DMARC
- well-known/brinker-international-well-known.yml — probed /.well-known/ across every host (all misses)
- authentication/brinker-international-authentication.yml — Apigee key/secret, approval-gated onboarding
- plans/brinker-international-plans-pricing.yml — plan_count 0, partner entitlement only
- rate-limits/brinker-international-rate-limits.yml — limit_count 0, nothing published

## Not present

No OpenAPI. No AsyncAPI. No GraphQL. No gRPC/Protobuf. No WSDL. No Postman collection.
No SDK or package on npm, PyPI, Maven Central, NuGet, RubyGems, crates.io or pkg.go.dev.
No CLI. No MCP server. No A2A agent card. No status page. No changelog. No sandbox.
No security.txt, no bug bounty, no trust center.