B
Brex REST APIs
Details
- URL
-
https://api.brex.com - Spec (json)
- https://developer.brex.com/_bundle/openapi/team_api.json?download
- Spec (json)
- https://developer.brex.com/_bundle/openapi/accounting_api.json?download
- Spec (json)
- https://developer.brex.com/_bundle/openapi/budgets_api.json?download
- Spec (json)
- https://developer.brex.com/_bundle/openapi/expenses_api.json?download
- Spec (json)
- https://developer.brex.com/_bundle/openapi/fields_api.json?download
- Spec (json)
- https://developer.brex.com/_bundle/openapi/onboarding_api.json?download
- Spec (json)
- https://developer.brex.com/_bundle/openapi/payments_api.json?download
- Spec (json)
- https://developer.brex.com/_bundle/openapi/transactions_api.json?download
- Spec (json)
- https://developer.brex.com/_bundle/openapi/travel_api.json?download
- Spec (json)
- https://developer.brex.com/_bundle/openapi/webhooks_api.json?download
- Spec (json)
- https://api.apis.guru/v2/specs/brex.io/2021.12/openapi.json
- Docs
- https://developer.brex.com/
Authentication
Authorization: Bearer <credential> Sign in to the Brex Dashboard as an account admin or card admin, open Settings → Developer, accept the developer API agreement if prompted, then click Create Token. Choose the scopes you need, confirm with Allow Access, and copy the token once shown. Brex says you won't be able to view it again; revoke and recreate it if lost.
OAuth 2.0 oauth2 discovered
OAuth 2.0 — self-onboarding
Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.