Brex API
A documented REST API at developer.brex.com covers expenses, payments, transactions, budgets, team, travel, and webhooks with OAuth 2.0 and granular scopes. User tokens work for in-house scripts, but production OAuth apps require partner registration, and there is no self-serve sandbox.
Frequently asked questions
Brex scores C on Supergood's API Report Card. A documented REST API at developer.brex.com covers expenses, payments, transactions, budgets, team, travel, and webhooks with OAuth 2.0 and granular scopes. User tokens work for in-house scripts, but production OAuth apps require partner registration, and there is no self-serve sandbox.
Brex has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Brex is an AI-native corporate-card and spend-management platform built around the Brex Empower product suite.
Vertical: Financial Services, corporate cards, spend management, AP/bill pay, and T&E for venture-backed startups, mid-market, and enterprise finance teams. Finance/ops onboard Brex during company formation or migration off Amex + Expensify + Bill.com.
Brex reports ~$700M in 2025 revenue (up from ~$500M in 2024), tens of thousands of business customers, and a customer roster heavy on Fortune 1000 and unicorn logos through the Empower platform.
Yes, for any company that runs cards, T&E, AP/bill pay, travel, or treasury through Brex, it is the system of record for the spend stack.
Founded 2017 in San Francisco by Henrique Dubugras (CEO) and Pedro Franceschi (CTO), both ex-Pagar.me founders.
Production OAuth credentials require Brex Partner registration and review, slowing third-party integration ship cycles. Access tokens expire every 3600 seconds (1 hour) requiring refresh-token rotation logic on every partner integration. Full sourced list under Sources below.
Common alternatives include Ramp, BILL Spend & Expense (Divvy), SAP Concur, Coupa, Bill.com, Expensify. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Brex has partial MCP support. No official MCP server from Brex, but a community server for the Brex API covering expense and transaction data is published on GitHub and npm with install instructions for Claude clients. Adoption is modest and Brex has not endorsed it.
Partially. MCP support for Brex exists but is incomplete, so what MCP clients like Claude, Cursor, and Codex can reach depends on what the available server covers.