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

Brushfire PaymentProfiles API

The PaymentProfiles API from Brushfire — 4 operation(s) for paymentprofiles.

Brushfire PaymentProfiles API is one of 16 APIs that Brushfire publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include PaymentProfiles. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 4 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 2025-07-22.

Requests are made against a single base URL, https://api.brushfire.com.

5 operations 4 paths 11 schemas 4 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2025-07-22
Base URL
https://api.brushfire.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Brushfire PaymentProfiles API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (apiKey).

  • apiKey — The App Key you received from https://developer.brushfire.com/key

Paths & Operations 5

Across 4 paths, the API surfaces 5 operations — 4 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

PaymentProfiles 5
GET
/paymentprofiles
Returns all payment profiles for the specified client
1 param → 200400
GET
/paymentprofiles/{paymentProfileId}
Returns the details of the specified payment profile
1 param → 200400
GET
/paymentprofiles/{paymentProfileId}/locations
Returns the locations associated with the merchant ID of a given payment profile.
1 param → 200400
GET
/paymentprofiles/{paymentProfileId}/terminals
Returns all terminals registered to the account associated with the supplied payment profile
1 param → 200400
POST
/paymentprofiles/{paymentProfileId}/terminals
Add a terminal to the supplied payment profile
1 param body → 200400

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are PaymentProfileConfigOutput (16 properties), PaymentProfileSingleOutput (13 properties), PaymentProfileListOutput (13 properties), LocationSingleOutput (5 properties). Each schema is shown below with its type and property counts.

LocationSingleOutput
object
5 properties
TerminalOutput
object
4 properties
PaymentProfileSingleOutput
object
13 properties
ApiModelError
object
4 properties
StringStringKeyValuePair
object
2 properties
PaymentProfileConfigInvoiceItem
object
3 properties
PaymentProfileListOutput
object
13 properties
PaymentProfileConfigOutput
object
16 properties
TerminalCreateInput
object
2 properties
TerminalCreateOutput
object
3 properties
PaymentMethodListOutput
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

brushfire-paymentprofiles-api-openapi.yml Raw ↑

Other APIs Brushfire publishes across the network.

Brushfire AccessCodes API
Brushfire Accounts API
Brushfire Attendees API
Brushfire Cart API
Brushfire Clients API
Brushfire Data API
Brushfire Events API
Brushfire Exchanges API
Brushfire Groups API
Brushfire Hooks API
Brushfire Lookups API
Brushfire Orders API
Where this information came from

This is an independent, third-party profile of Brushfire PaymentProfiles 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.