> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/finance-and-accounting/brex/common-issues.md).
# Common Issues
## Connection issues
My API key isn't being accepted
Double-check that you copied the full token from the Brex Developer Portal — tokens are long and it's easy to truncate them. Also confirm the token hasn't been revoked or expired. If you recently regenerated your key in Brex, the old one will stop working immediately. Create a new token and update it in your Coupler.io data flow settings.
The data flow fails with an authentication error
This usually means the API token doesn't have the required scopes. In the Brex Developer Portal, check that your token has **read** access for the entities you're trying to pull (e.g., Transactions, Expenses, Budgets). If you created a restricted token, expand its permissions or generate a new one with broader read access.
## Missing data
No transactions are showing up
Check your **start date** setting. If the date is set too recently or to a future date, no records will be returned. Use the date picker to set a start date that covers the period you expect data for. Also confirm that card transactions exist in Brex for that period — pending transactions may not appear depending on their state.
Some expenses are missing from the export
Expenses in **draft** status may not be returned by the API depending on your account's configuration. Only submitted or approved expenses are reliably available. Check the status of the missing expenses in Brex directly.
Departments or Vendors show fewer records than expected
The Departments and Vendors entities return all active records. If a department or vendor has been archived or deactivated in Brex, it may not appear. Check the Brex admin panel to confirm whether the missing records are still active.
## Permission errors
I get a 403 Forbidden error when running the data flow
Your API token exists but doesn't have permission to access the requested entity. This happens when tokens are created with limited scopes. Go to the Brex Developer Portal, review the token's permissions, and make sure it includes read access for the specific entity (e.g., `expenses.readonly`, `budgets.readonly`). Update the token or generate a new one with the right scopes.
Only some entities work — others return permission errors
Brex API tokens can be scoped per resource. If Transactions work but Budgets don't, your token likely lacks the budget scope. Review each required scope in the Brex Developer Portal and update your token accordingly.
## Data discrepancies
Transaction amounts differ from what I see in Brex
Pending transactions can change after they settle — the final amount may differ from what was captured at the time of the sync. If you're using scheduled refreshes, make sure you're pulling data frequently enough to capture settled values. Filtering your analysis to **settled** transactions only will give you the most accurate figures.
Budget remaining amounts don't match the Brex dashboard
Budget data reflects a snapshot at the time of the sync. If spending occurred after the last run, the remaining amount will be out of date. Run the data flow again to get the latest figures.
## Rate limits
The data flow is failing or timing out on large exports
Brex enforces API rate limits that may affect large data pulls. If you're pulling a long date range of Transactions or Expenses, try narrowing the start date to reduce the volume of records per run. Once you have a baseline, you can rely on scheduled incremental refreshes to keep data current without hitting limits.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.coupler.io/sources/category/finance-and-accounting/brex/common-issues.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.