Bread Financial · Authentication Profile

Bread Financial Authentication

Authentication

Authentication model for the Bread Pay developer surface, captured from the published API-access documentation (no OpenAPI securitySchemes were available to derive from). The next-generation BreadPay Platform API uses OAuth 2.0; the legacy sandbox/servicing API uses HTTP Basic plus a client token header.

Bread Financial secures its APIs with oauth2, http, and apiKey across 3 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyFintechPaymentsBuy Now Pay LaterLendingConsumer FinancePoint-of-SaleE-Commerce

Methods: oauth2, http, apiKey Schemes: 3 OAuth flows: clientCredentials API key in: header

Security Schemes

BreadPay OAuth 2.0 (client credentials) oauth2

Sandbox Basic Auth + client token http

scheme: basic

Merchant integration key apiKey

· in: header ()

Source

Authentication Profile

generated: '2026-07-18'
method: searched
source: https://platform-docs.breadpayments.com/bread-developers/docs/api-access
docs:
- https://platform-docs.breadpayments.com/bread-developers/docs/api-access
- https://docs.breadpayments.com/bread-classic/reference/getting-started-with-your-api
description: >-
  Authentication model for the Bread Pay developer surface, captured from the
  published API-access documentation (no OpenAPI securitySchemes were available
  to derive from). The next-generation BreadPay Platform API uses OAuth 2.0; the
  legacy sandbox/servicing API uses HTTP Basic plus a client token header.
summary:
  types: [oauth2, http, apiKey]
  oauth2_flows: [clientCredentials]
  api_key_in: [header]
schemes:
- name: BreadPay OAuth 2.0 (client credentials)
  type: oauth2
  flow: clientCredentials
  token_format: JWT
  detail: >-
    BreadPay Platform APIs use the OAuth 2.0 Client Credentials Flow for
    server-to-server (2-legged) interactions. Client credentials are sent using
    HTTP Basic Authentication (Base64 of client_id:client_secret) to the
    authorization server, which returns a JWT access token. Credentials are
    issued from the Bread Merchant Portal / by the Bread partnership team.
  source: https://platform-docs.breadpayments.com/bread-developers/docs/api-access
- name: Sandbox Basic Auth + client token
  type: http
  scheme: basic
  detail: >-
    The partner sandbox / enterprise servicing API requires HTTP Basic Auth
    (Base64 of client_id:client_secret) in the Authorization header PLUS a
    separate client_token header (alphanumeric, up to 50 chars) designated by
    Bread Financial. Requests must also originate from an allow-listed IP range.
  source: https://platform-docs.breadpayments.com/bread-onboarding/docs/sandbox-access
- name: Merchant integration key
  type: apiKey
  in: header
  detail: >-
    Browser SDK and Bread Classic checkout flows are initialized with a merchant
    integrationKey (public) that identifies the merchant program; server-side
    Classic calls additionally use an API key + shared secret.
  source: https://docs.breadpayments.com/bread-classic/reference/getting-started-with-your-api

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/bread-financial-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.