How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

BreadPay Merchant Operations API

The merchant-facing transaction lifecycle — authorize, settle, refund, cancel, rescind, extend expiration — plus carts, fulfillment detail, and settlement/funding/targeting reporting exports. Transaction state changes are guarded by an ETag/If-Match revision check that answers 412 on a mismatch. 32 operations.

BreadPay Merchant Operations API is one of 13 APIs that Bread Financial publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transactions, Settlement, Refunds, Reporting, and Carts. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 32 operations across 26 paths, organized into 3 resource areas, and defines 89 schemas. It is described by OpenAPI 3.0.3, at version 2.0.0.

Requests are made against 2 base URLs: https://api-preview.platform.breadpayments.com/, https://api.platform.breadpayments.com/.

32 operations 26 paths 89 schemas 1 DELETE18 GET2 PATCH11 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2.0.0
Base URL
https://api.platform.breadpayments.com
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer
Resource Areas
3

Authentication & Security 3

BreadPay Merchant Operations API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuthTransaction). It accepts HTTP bearer tokens (JWT) (bearerAuthCarts). It accepts HTTP bearer tokens (JWT) (bearerAuthReporting).

  • bearerAuthTransaction — The JWT access token provided by the Auth service.
  • bearerAuthCarts — The JWT access token provided by the Auth service.
  • bearerAuthReporting — The JWT access token provided by the Auth service.

Paths & Operations 32

Across 26 paths, the API surfaces 32 operations — 1 DELETE, 18 GET, 2 PATCH, 11 POST. They span 3 resource areas: Transaction, Cart, Reporting. Each is listed below with its method, path, parameters, and response codes.

Transaction 18
GET
/api/transaction/application/{applicationID}
Get Transaction by Application ID
getTransactionByApplicationID 1 param → 200401403404500503
GET
/api/transaction
List Transactions
listTransactions 15 params → 200401403404500503
GET
/api/transaction/searchdeprecated
Search Transactions
searchTransactions 18 params → 200401403404500503
POST
/api/transaction/search
Search Transactions By Keyword
searchTransactionsByKeyword 7 params → 200401403404500503
GET
/api/transaction/{transactionID}
Get Transaction by Transaction ID
getTransactionByID 2 params → 200401403404500503
PATCH
/api/transaction/{transactionID}
Update Transaction
updateTransaction 1 param body → 200401403500503
POST
/api/transaction/{transactionID}/extend-expiration
Extend Expiration
extendExpiration 1 param → 200400401403404500503
POST
/api/transaction/{transactionID}/rescind
Rescind Transaction
rescindTransaction 2 params → 200400401403404412500503
GET
/api/transaction/{transactionID}/history
Get Transaction History
getTransactionHistory 1 param → 200401403404500503
GET
/api/transaction/{transactionID}/fulfillment
Get Transaction Fulfillment Details
getFulfillmentDetail 1 param → 200401403404500503
POST
/api/transaction/{transactionID}/fulfillment
Add Transaction Fulfillment Detail
addFulfillmentDetail 1 param body → 200401403404409500503
POST
/api/transaction/{transactionID}/authorize
Authorize Transaction
authorizeTransaction 2 params body → 200400401403412500503
POST
/api/transaction/{transactionID}/cancel
Cancel Transaction
cancelTransaction 2 params body → 200400401403412500503
POST
/api/transaction/{transactionID}/refund
Refund Transaction
refundTransaction 2 params body → 200400401403412500503
POST
/api/transaction/{transactionID}/settle
Settle Transaction
settleTransaction 2 params body → 200400401403412500503
GET
/api/transaction/kpi
Transaction KPIs
kpi 4 params → 200400401403500503
GET
/api/transaction/aggregation
Transaction Aggregation
aggregation 14 params → 200400401403500503
GET
/api/reporting/report/transaction
List Transactions CSV
listTransactionsCSV 19 params → 200401403404500503
Cart 7
GET
/api/cart
List carts
getCarts 7 params → 200401403404500
POST
/api/cart
Create a Cart
createCart body → 201401403500
GET
/api/cart/{id}
Get Cart
getCartByID 1 param → 200401403404410500
PATCH
/api/cart/{id}
Update Cart information
updateCart 1 param body → 200401403404410422500
DELETE
/api/cart/{id}
Delete Cart
deleteCart 1 param → 204401403404422500
POST
/api/cart/{id}/expire
Expire Cart
expireCart 1 param → 204401403404410422500
POST
/api/cart/{id}/notify
Notify Buyer
notifyBuyer 1 param → 204401403404410422500
Reporting 7
GET
/api/reporting/report/loan-historydeprecated
Get Loan History Report By Name
getLoanHistory 7 params → 200401403500503
GET
/api/reporting/report/data-insight
Get Data Insight Report By Name
getDataInsight 9 params → 200401403500503
GET
/api/reporting/report/funding-aggregate-summary
List funding aggregate balance data
listFundingAggregateSummaryJSON 6 params → 200400401403500503
GET
/api/reporting/report/targeting-export
List targeting export CSV
listTargetingExportCSV 9 params → 200401403404500503
GET
/api/reporting/report/settlement-report
List settlement report CSV
listSettlementReportCSV 11 params → 200400401403404500503
GET
/api/reporting/report/settlement-report-legacy
Get legacy settlement report
getLegacySettlementReport 8 params → 200400401403404500503
GET
/api/reporting/report/funding-daily-summarydeprecated
List funding daily balance data
listFundingDailySummaryJSON 8 params → 200400401403500503

Schemas 89

The contract defines 89 schemas that model the data the API accepts and returns. The most detailed are Transaction (33 properties), LegacySettlementReportEntry (27 properties), CartResponse (14 properties), CreateCart (13 properties). Each schema is shown below with its type and property counts.

TransactionMetadata
object
Metadata is a JSON field available to merchants for storing external data on a Transaction Metadata keys have a max size of 128, and there can be up to 50 keys…
TransactionListSort
string
The possible sort keys for listing Transactions
TransactionStatus
string
The possible statuses of a Transaction
ExternalID
string
An identifier that has significance to the Merchant allowing the transaction to be associated with the Merchant’s systems.
Transaction
object
Transaction is a representation of a single transaction
33 properties 31 required
TransactionHistoryType
string
The type of action that was performed for a given part of a transaction's history.
TransactionHistory
object
An action that was performed on a transaction.
8 properties 8 required
KPI
object
A key performance indicator for a particular transaction status. This is an aggregation across many transactions.
7 properties 7 required
Aggregation
object
An instance of an aggregated object
2 properties 2 required
AggregationTerm
string
The possible aggregation terms
UpdateRequest
object
Object to modify an existing transaction.
2 properties
ActionRequest
object
Object for performing actions like authorizations, refunds, and cancellations.
4 properties 1 required
Pagination
object
Result pagination values
3 properties
TransactionList
object
all metadata and data related to a requested report
7 properties
AggregationList
object
1 property 1 required
KPIList
object
An array of key performance indicators
1 property 1 required
TransactionHistoryList
object
An array containing the points of history in a single transaction.
1 property 1 required
FulfillmentDetail
object
Fulfillment detail, carrier and tracking number, for a transaction
5 properties 4 required
FulfillmentDetailRequest
object
2 properties 1 required
FulfillmentDetailList
object
An array containing all the fulfillment details for a single transaction.
1 property 1 required
CreateCart
object
Payload that is sent to the Cart service to create a Cart
13 properties 3 required
CartContact
object
Represents buyer information that is associated with the Cart object
5 properties 4 required
CartID
string
CartID associated with a Cart
CheckoutCompleteURL
string
URL that the customer is redirected to following a successful checkout
CallbackURL
string
Where we'll POST the transactionID of the checkout and the orderRef following a successful checkout.
CheckoutErrorURL
string
URL the user is redirected to if checkout fails
CheckoutURL
string
URL to Checkout using the associated Cart
CartStatus
string
The current status of the Cart. Generated when returning a Cart object.
OrderReference
string
Unique identifier provided by the merchant. Appended to the CheckoutCompleteURL after a Cart is complete.
CartListSort
string
The possible sort keys for listing Carts
PageLimit
string
The maximum number of records that will be returned in a result set.
PageOffset
string
The number of records to skip before starting to collect the result set. Used in conjunction with limit query parameter for pagination support
PageTotal
string
The total number of records in the result set
CartUpdate
object
Object to modify an existing Cart
9 properties
CartResponse
object
Cart object
14 properties
ListCart
object
Cart object for list
10 properties
PageInfo
object
Describes the limit, offset and total records in the current request
3 properties
CartListResponse
object
2 properties
CartDisclosures
array
CartDisclosure
object
Disclosure object
2 properties
ReportingError
Default error model for Reporting errors.
LoanHistoryReport
object
all metadata and data related to a requested report
7 properties 2 required
DataInsightReport
object
all metadata and data related to a requested report
7 properties 2 required
Schema
object
dictates the Header row of a CSV response
1 property
Field
object
describes a field of data returned
2 properties 1 required
LoanValue
object
the total value of all loans
2 properties
LoanVolume
object
the total volume of all loans
2 properties 1 required
LoanAggregate
object
aggreagtion of transaction loan data
4 properties
DataInsightPoint
object
aggregate data point for the given date or date range
11 properties 8 required
Aggregate
object
aggregate data for the given date or date range
11 properties 8 required
ValuePerPPType
object
shows the total values per payment product type
4 properties 1 required
LoanHistory
object
Loan history for a given merchantID and date range
6 properties
DataInsight
object
Data insight for a given merchantID and date range
4 properties
FundingAggregateSummary
object
A summary of the funding data
7 properties
TransactionError
Default error model for ListTransaction errors.
FundingDailySummaryList
object
A summary of daily funding data
7 properties
TargetingExportList
object
all metadata and data related to a targeting export report
7 properties
SettlementReportList
object
all metadata and data related to a settlement report
7 properties
LegacySettlementReport
object
2 properties
LegacySettlementReportEntry
object
Settlement report entry is a record of an individual funding event.
27 properties
CountryCode
string
The two character ISO-3166-1 country code.
Region
string
The region or first-level administration division (e.g. State/Province) of the address.
CurrencyCode
string
The three letter currency code as defined in ISO 4217.
LanguageCode
string
The two language code as defined in ISO 639-1 along with subtags tag if applicable.
Money
object
Represents a monetary amount in the specified currency
2 properties 2 required
Phone
string
Telephone number including country code
Email
string
Email address
Percentage
number
Percentage value
BasisPoint
integer
A value which represents one-hundredth of one percent.
Date
string
The date value formatted per RFC3339. This does not allow nulls.
NullDate
string
The date value formatted per RFC3339. This allows nulls.
Timestamp
string
The timestamp value formatted per RFC3339. This does not allow nulls.
NullTimestamp
string
The timestamp value formatted per RFC3339. This does allow nulls.
UUID
string
A universally unique identifier (Version 4) as defined in RFC4122. This does not allow nulls.
NullUUID
string
A universally unique identifier (Version 4) as defined in RFC4122. This allows nulls.
Address
object
Represents a fully defined address for an entity
6 properties 5 required
Name
object
Represents the full name
3 properties 2 required
Contact
object
Represents contact information for an entity
4 properties 1 required
BankAccountDetail
object
Bank account detail definition
6 properties 4 required
BusinessIdentity
object
Identity for a business
2 properties 2 required
PersonIdentity
object
Identity for a person
2 properties 2 required
BankIdentifier
object
2 properties 2 required
PaymentProductType
string
The type of payment product
TermInterval
string
Defines set of valid term intervals for a payment product
Terms
object
Represents the terms offered for a payment product
4 properties 4 required
AsLowAs
object
Represents a sample offer with the appropriate user prompts for a given amount and apr along with apr bounds
6 properties 6 required
Identity
object
The claims that determines the access level of the caller.
5 properties 1 required
Error
object
1 property 4 required
BaseError
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bread-merchant-operations-openapi.json Raw ↑

Other APIs Bread Financial publishes across the network.

BreadPay Platform API
Bread Pay API
Bread SplitPay API
BreadPay Checkout API
Bread SplitPay
BreadPay Servicing API
BreadPay Buyer Management API
BreadPay Payments API
BreadPay Foundations API
BreadPay Webhook API
BreadPay Program API
BreadPay Tradein API
Where this information came from

This is an independent, third-party profile of BreadPay Merchant Operations API, 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.