Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.alterauth.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Connect your users to Brex for corporate card management, expense tracking, and financial data access.
PropertyValue
Provider IDbrex
CategoryFinance
PKCESupported
Token refreshAutomatic
Redirect URIShown in Developer Portal

​
Step 1: Get Brex OAuth credentials

Brex OAuth (3LO) is partner-gated — there is no self-serve developer console for creating OAuth apps. Credentials must be issued by Brex’s developer support team after the partner application is approved.
1

Apply to be a Brex developer partner

Submit an application at brex.com/partners.
2

Request OAuth credentials

Once approved, contact the Brex developer support team to request OAuth client credentials. Provide the Alter callback URL from the Developer Portal — Brex configures the redirect URI on its side, there is no self-serve UI for it.
3

Receive credentials

Brex issues a Client ID, Client Secret, and the list of approved scopes.
For internal automations against a single Brex account (not user-facing OAuth), use a User Token generated under Developer → Settings at dashboard.brex.com instead — that flow uses a static bearer token, not OAuth, and does not work with this provider.
Never share your Client Secret publicly. Store it securely and only enter it in the Alter Vault Developer Portal.

​
Step 2: Add to Alter Vault

1

Open the Developer Portal

Go to portal.alterauth.com and navigate to your app.
2

Add Brex provider

Go to OAuth Providers > Add Provider > Brex.
3

Enter credentials

  • Client ID: Paste your Brex Client ID
  • Client Secret: Paste your Brex Client Secret
4

Select scopes

Choose the scopes your app needs.
5

Save

Click Save. The provider is now active.

​
Available Scopes

ScopeDescription
openidOpenID Connect authentication
offline_accessRequest a refresh token for long-lived access
transactions.card.readonlyRead-only access to card transactions
accounts.card.readonlyRead-only access to card accounts
users.readonlyRead-only access to user information
expenses.cardAccess to card expense data
budgets.readonlyRead-only access to budgets
vendors.readonlyRead-only access to vendor information
Include both openid and offline_access scopes to enable automatic token refresh.

​
Notes

  • The openid and offline_access scopes are included by default.
  • Brex scopes configured in your OAuth application must match the scopes you request during authorization.