> 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/faq.md).

# FAQ

<details>

<summary>Where do I find my Brex API key?</summary>

Log in to Brex and go to **Settings > Developer**. From there you can generate a new API token. Make sure to copy it immediately — Brex won't show it again after you navigate away. Paste it into the API key field when setting up your Brex source in Coupler.io.

</details>

<details>

<summary>Can I connect multiple Brex accounts to Coupler.io?</summary>

Yes. Each Brex account has its own API token. Create a separate source in Coupler.io for each account and use the **Append** transformation to merge their data into a single destination. This gives you a unified view of spending across all accounts.

</details>

<details>

<summary>Which entities support date filtering?</summary>

The **start date** parameter applies to Transactions and Expenses, which are time-series entities. Budgets, Users, Departments, and Vendors return all available records and aren't filtered by date.

</details>

<details>

<summary>Why do my transaction amounts keep changing between syncs?</summary>

Brex transactions start as **pending** and update when they settle. The final settled amount can differ from the pending estimate. This is expected behavior — refresh your data flow daily and filter to settled transactions when building financial reports.

</details>

<details>

<summary>Can I use Brex data with AI tools like ChatGPT or Claude?</summary>

Yes. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. You can send your Brex Transactions or Expenses data directly to these tools to generate spend summaries, flag unusual activity, or draft budget commentary.

</details>

<details>

<summary>Can I combine Brex data with other financial tools?</summary>

Absolutely. You can add multiple sources to a single Coupler.io data flow. For example, join Brex Transactions with data from your accounting software or ERP to reconcile records. Use the **Join** or **Append** transformations depending on whether you're enriching rows or stacking datasets.

</details>

<details>

<summary>How do I pull data for a specific department only?</summary>

Brex doesn't currently support department-level filtering at the API level. Pull all Transactions or Expenses and then filter by department in your destination — Google Sheets, Looker Studio, or BigQuery all make this straightforward.

</details>

<details>

<summary>Do I need admin access to generate a Brex API key?</summary>

Yes, generating API tokens in Brex typically requires admin access to the Developer settings. If you don't have admin rights, ask your Brex account administrator to generate a read-only token for you.

</details>

{% hint style="info" %}
For details on what fields are available in each entity, see [Data Overview](/sources/category/finance-and-accounting/brex/data-overview.md). If your data flow is failing or returning unexpected results, check [Common Issues](/sources/category/finance-and-accounting/brex/common-issues.md). For tips on structuring your data flow efficiently, visit [Best Practices](/sources/category/finance-and-accounting/brex/best-practices.md).
{% endhint %}


---

# 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/faq.md?ask=<question>&goal=<endgoal>
```

`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.