Obtain a Brex API token from the Brex dashboard (developer settings) or via OAuth 2.0 for third-party integrations; include it as Authorization: Bearer YOUR_TOKEN on all requests.
GET https://platform.brexapis.com/v2/transactions/card/primary to retrieve card transactions; use cursor and limit query parameters for pagination.
Each transaction object includes fields such as amount (with currency and amount subfields), merchant, initiated_at_date, and description.
For cash/ACH transactions, use GET https://platform.brexapis.com/v2/transactions/cash/{account_id} with the appropriate account ID.
To retrieve expense categorization and accounting attributes attached to transactions, use the expenses API endpoints under /v1/expenses.
Iterate through all pages using the next_cursor value from each response until next_cursor is null.
Known gotchas
Brex amounts are represented in the smallest currency unit (e.g., cents for USD); divide by 100 before displaying or posting to a general ledger.
The primary card transaction endpoint returns only primary card account transactions; teams using multiple Brex accounts must query each account separately.
Brex token scopes vary; ensure the token was issued with the transactions.readonly scope or equivalent, otherwise API calls return 403.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp