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

# Brex

Connect Brex to Coupler.io to pull transactions, expenses, budgets, and spend data into Google Sheets, BigQuery, or your warehouse.

Brex is a financial platform built for businesses, offering corporate cards, expense management, and budgeting tools. Connecting Brex to Coupler.io lets you pull your spending data — transactions, expenses, budgets, and more — into any destination for reporting and analysis.

## Why connect Brex to Coupler.io?

* **Centralize financial data** — combine Brex transactions and expenses with data from other tools like your accounting software or ERP
* **Automate spend reporting** — keep dashboards in Google Sheets, Looker Studio, or Power BI updated without manual exports
* **Feed AI tools** — send your spending data to ChatGPT, Claude, or Gemini to summarize trends, flag anomalies, or draft budget narratives
* **Join entities** — combine transactions with departments and users to see who's spending what and where

## Prerequisites

* A Brex account with admin or developer access
* A Brex API key (generated from the Brex Developer Portal under **Settings > Developer**)

## Quick start

{% hint style="success" %}
Start with the **Transactions** entity — it's the most data-rich and gives you an immediate view of card spending. Combine it with **Departments** or **Users** using a Join transformation to get a full picture.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to Coupler.io, go to your workspace, and click **Add data flow**. Search for **Brex** and select it as your source.
{% endstep %}

{% step %}
**Enter your Brex API key.** In the Brex Developer Portal, navigate to **Settings > Developer** and generate a new API token. Copy the token and paste it into the API key field in Coupler.io.
{% endstep %}

{% step %}
**Select an entity.** Choose the data you want to pull — Transactions, Expenses, Budgets, Users, Departments, or Vendors. You can add more sources to the same data flow later.
{% endstep %}

{% step %}
**Set a start date.** Use the date picker to define how far back you want to pull data. This applies to time-based entities like Transactions and Expenses.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT or Claude.
{% endstep %}

{% step %}
**Run the data flow.** Click **Run** to execute your first manual sync. Once it completes successfully, your data will appear in the destination and you can set up a schedule.
{% endstep %}
{% endstepper %}

## Brex data overview

Brex exposes six entities through Coupler.io, covering the full lifecycle of business spending — from card swipes to budget allocations. Here's what each entity contains and how you can use the data.

## Entities overview

| Entity       | Best used for                                     |
| ------------ | ------------------------------------------------- |
| Transactions | Spend analysis, reconciliation, merchant tracking |
| Expenses     | Reimbursement tracking, policy compliance         |
| Budgets      | Budget vs. actual reporting, remaining funds      |
| Users        | Headcount-based spend allocation, access audits   |
| Departments  | Department-level cost center reporting            |
| Vendors      | Supplier payment tracking, vendor analysis        |

## Transactions

#### Key fields

| Field          | Description                                |
| -------------- | ------------------------------------------ |
| Transaction ID | Unique identifier for each transaction     |
| Amount         | Transaction value in the account currency  |
| Currency       | Currency code (e.g., USD)                  |
| Date           | Date the transaction was posted            |
| Merchant name  | Name of the merchant or vendor             |
| Status         | Current state (e.g., pending, settled)     |
| Card holder    | The user who made the transaction          |
| Department     | Department associated with the transaction |
| Category       | Spend category (e.g., travel, software)    |

## Expenses

#### Key fields

| Field        | Description                                          |
| ------------ | ---------------------------------------------------- |
| Expense ID   | Unique identifier for the expense                    |
| Amount       | Submitted expense amount                             |
| Currency     | Currency of the expense                              |
| Status       | Submission status (e.g., draft, submitted, approved) |
| Submitted by | User who submitted the expense                       |
| Merchant     | Merchant associated with the expense                 |
| Category     | Expense category                                     |
| Memo         | User-provided note or description                    |

## Budgets

#### Key fields

| Field            | Description                             |
| ---------------- | --------------------------------------- |
| Budget ID        | Unique identifier for the budget        |
| Budget name      | Name of the budget (e.g., Q3 Marketing) |
| Owner            | Person responsible for the budget       |
| Limit amount     | Total spending limit                    |
| Spent amount     | Amount spent so far                     |
| Remaining amount | Funds still available                   |
| Period           | Time period the budget covers           |
| Department       | Department the budget belongs to        |

## Users

#### Key fields

| Field      | Description                                |
| ---------- | ------------------------------------------ |
| User ID    | Unique identifier for the user             |
| Name       | Full name of the employee                  |
| Email      | Work email address                         |
| Role       | User role (e.g., admin, employee)          |
| Department | Department the user belongs to             |
| Status     | Account status (e.g., active, deactivated) |

## Departments

#### Key fields

| Field             | Description                                      |
| ----------------- | ------------------------------------------------ |
| Department ID     | Unique identifier for the department             |
| Department name   | Name of the department                           |
| Parent department | Parent in a department hierarchy (if applicable) |

## Vendors

#### Key fields

| Field       | Description                      |
| ----------- | -------------------------------- |
| Vendor ID   | Unique identifier for the vendor |
| Vendor name | Name of the merchant or supplier |
| Category    | Vendor category                  |

## Common field combinations

* **Transactions + Users** — see per-employee spend using a Join on User ID
* **Transactions + Departments** — build department-level cost center reports
* **Expenses + Budgets** — compare submitted expenses against budget limits
* **Budgets + Departments** — track budget utilization across cost centers

## Use cases by role

{% tabs %}
{% tab title="Finance teams" %}

* Pull Transactions and Expenses into BigQuery or Google Sheets for month-end close reconciliation
* Join Budgets with Departments to generate budget vs. actual reports for each cost center
* Use Aggregate transformations to roll up spend by category, department, or time period
* Send budget summaries to Claude or ChatGPT to auto-generate executive spend narratives
  {% endtab %}

{% tab title="Operations" %}

* Monitor Vendors to track which suppliers are receiving payments and flag new or unexpected merchants
* Keep a live Departments snapshot to maintain an up-to-date cost center structure for reporting
* Append Transactions data from multiple Brex accounts (if you manage more than one) into a single destination
  {% endtab %}

{% tab title="HR & People teams" %}

* Use the Users entity to audit who has active Brex access and align it with your HR system
* Track expense submission patterns by employee to identify outliers or policy gaps
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* The **start date** parameter applies to time-series entities (Transactions, Expenses). For Budgets, Users, Departments, and Vendors, all available records are returned regardless of date.
* Transactions with a **pending** status may change after settlement — consider refreshing data daily if you need accurate settled amounts.
* Brex API access requires a token with appropriate scopes. A read-only token is sufficient for all Coupler.io entities.
* If your organization uses multiple Brex accounts, you'll need a separate API key per account. Use the **Append** transformation in Coupler.io to merge data into one destination table.

## Brex common issues

### Connection issues

<details>

<summary>My API key isn't being accepted</summary>

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.

</details>

<details>

<summary>The data flow fails with an authentication error</summary>

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.

</details>

### Missing data

<details>

<summary>No transactions are showing up</summary>

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.

</details>

<details>

<summary>Some expenses are missing from the export</summary>

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.

</details>

<details>

<summary>Departments or Vendors show fewer records than expected</summary>

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.

</details>

### Permission errors

<details>

<summary>I get a 403 Forbidden error when running the data flow</summary>

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.

</details>

<details>

<summary>Only some entities work — others return permission errors</summary>

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.

</details>

### Data discrepancies

<details>

<summary>Transaction amounts differ from what I see in Brex</summary>

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.

</details>

<details>

<summary>Budget remaining amounts don't match the Brex dashboard</summary>

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.

</details>

### Rate limits

<details>

<summary>The data flow is failing or timing out on large exports</summary>

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.

</details>

## Brex 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](#brex-data-overview). If your data flow is failing or returning unexpected results, check [Common Issues](#brex-common-issues). For tips on structuring your data flow efficiently, visit [Best Practices](https://docs.coupler.io/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/finance-and-accounting/brex.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
