A token without the scope for a data group cannot read that group. User tokens expire after 90 days without API use.
Before you start
- A Brex user token with read scopes for the data to sync.
1. Open Brex Developer settings
Open Brex Dashboard → Developer and select Create token.
2. Choose read scopes
Grant the read scopes you want Permute to sync, such as Team, Transactions, Expenses, Budgets, or Vendors.
Create a user token in Brex Dashboard → Developer. Brex asks you to select scopes when you create it. Include read scopes for each data group you want in Permute, such as transactions, expenses, budgets, vendors, or team data.
A token carries the scopes chosen for it. If a data group is missing, inspect those scopes.
3. Copy the user token
Copy the user token.
Brex shows the full token when you create it, then hides part of it in the dashboard. Copy it directly into Permute’s API Key field. If you lose the full value, create another token.
Revoke a token in Brex when it is no longer needed or may have been exposed. Calls using a revoked token fail at once.
4. Add Brex in Permute
In your workspace, open Connectors, select Add Connector, choose Brex, and name the account.
Under Sync which data?, choose an option:
| Choice | What it does |
|---|---|
| Everything | Selects all discovered data available to this connection. |
| Select manually | Choose the tables Permute syncs. |
- Paste the token into API Key and select Connect.
5. Choose tables (manual selection)
If you chose Select manually, open the connector after connecting. Use the checkboxes to select at least one table, then select Save selection.
6. Check the first result
- Choose a Brex transaction or expense that exists in the account tied to the token.
- Compare its data group with the token’s read scope before checking other groups.
Available data
| Data group | What the setup screen covers |
|---|---|
| Spending | Transactions, expenses, and budgets. |
| People and payees | Team and vendor data. |
Match scopes to data groups
Brex lists separate read scopes for budgets, card expenses, vendors, users, and card or cash transactions. For example, budgets.readonly permits budget data; expenses.card.readonly permits card expense data; vendors.readonly permits vendor data. Transaction scopes distinguish card from cash transactions.
Choose the scopes for the groups named on the Permute setup screen. A token with only card transaction access does not also grant budget or vendor access. If one group is missing while others sync, compare its specific read scope with the token you created.
Access and source details
Plan for token ownership
A Brex user token belongs to the person who made it. Brex stops accepting the token when that user becomes inactive. Choose an appropriate user for a long-lived connection and review ownership before that person’s status changes.
The Developer page shows created tokens with part of each value hidden. Keep a record of which token serves Permute so you can revoke or replace the correct one.
Troubleshooting
| Problem | What to check |
|---|---|
| One group is absent | Check that the token has its Brex read scope. |
| A working token stops | Check whether it expired or its user became inactive. |