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 Orders API

The Orders API from Brushfire — 11 operation(s) for orders.

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

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

This API exposes 13 operations across 11 paths, and defines 30 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.

13 operations 11 paths 30 schemas 5 GET8 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 Orders 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 13

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

Orders 13
GET
/orders
Gets list of orders by eventId and/or a date range.
3 params → 200400
POST
/orders
Create an order from an existing cart
body → 200400
GET
/orders/{orderId}
Retrieve a single order
3 params → 200400
GET
/orders/{orderId}/fields
Retrieve fields for an order
2 params → 200400
POST
/orders/{orderId}/fields
Update fields for an order
1 param body → 200400
GET
/orders/{orderId}/print
Retrieve the printable resources for a single order
4 params → 200400
POST
/orders/{orderId}/resend
Resend a confirmation for a single order
1 param body → 200400
POST
/orders/direct
Create cart-less order for free, general admission events with no fields.
body → 200400
GET
/orders/helpdesk/{email}
Retrieve orders that match provided email
1 param → 200400
POST
/orders/pos
Create a point of sale order from an existing cart
body → 200400
POST
/orders/print
Retrieve the printable resources for multiple orders
body → 200400
POST
/orders/reader/start
Prepares an order to be paid for with a Square or Stripe Reader.
body → 200400
POST
/orders/sms
Sends SMS messages to the provided phone number (only US and Canada)
body → 200400

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are OrderSingleOutput (54 properties), OrderAttendeeSummaryOutput (42 properties), OrderListOutput (42 properties), OrderCreateInput (35 properties). Each schema is shown below with its type and property counts.

OrderAttendeeSummaryOutput
object
42 properties
OrderReaderStartOutput
object
6 properties
OrderSmsInput
object
2 properties
UnitFeeLineItemOutput
object
A single fee or tax line item evaluated for an attendee from the attendee type's customFees configuration. On cart outputs this is a live evaluation; on order…
3 properties
DomainValidationOutput
object
2 properties
PrintType
string
InvoiceRelativeDays
string
OrderCreateOutput
object
3 properties
FieldInput
object
2 properties 1 required
FeeItemType
string
OrderCreateDirectInput
object
18 properties 4 required
OrderSingleOutput
object
54 properties
StringStringKeyValuePair
object
2 properties
OrderPrintInput
object
4 properties 2 required
FieldUpdateInput
object
3 properties
OrderListOutput
object
42 properties
OrderHelpdeskOutput
object
13 properties
OrderReaderStartInput
object
10 properties 3 required
OrderCreateInput
object
35 properties 9 required
OrderConfirmationResendInput
object
1 property
OrderPromotionOutput
object
2 properties
OrderCreatePOSInput
object
29 properties 3 required
OrderListPaymentOutput
object
8 properties
OrderResultOutput
object
11 properties
FieldOptionFullOutput
object
14 properties
ApiModelError
object
4 properties
FieldOutput
object
27 properties
OrderRelationshipPaymentOutput
object
3 properties
OrderRelationshipOutput
object
7 properties
PrintFormat
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

brushfire-orders-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 PaymentProfiles API
Where this information came from

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