# Brex integrations: cards, expenses and vendors

> Create a card, upload a receipt and create a vendor in Brex, and start a workflow when Brex sends “Expense payment updated”.

**Canonical page:** https://tray.ai/connectors/brex-integrations/
**Categories:** Finance
**Connects through:** HTTP Connector

## Overview

Brex is a spend management platform that combines corporate cards, expense tracking, bill pay and budgets for finance teams. Tray.ai connects to Brex through the HTTP Connector, so your workflows can call the Brex API alongside the rest of your stack.

## Use cases

### Users

Read, create, and update users in Brex from any Tray.ai workflow. The Brex API covers calls such as list users and get a user.

- List users
- Get a user
- Invite a user

### Cards

Read, create, and update cards in Brex from any Tray.ai workflow. The Brex API covers calls such as list cards and create a card.

- List cards
- Create a card
- Update a card

### Expenses

Read, create, and update expenses in Brex from any Tray.ai workflow. The Brex API covers calls such as list expenses and get an expense.

- List expenses
- Get an expense
- Update an expense

### Vendors

Read, create, update, and delete vendors in Brex from any Tray.ai workflow. The Brex API covers calls such as list vendors and create a vendor.

- List vendors
- Create a vendor
- Update a vendor

### Transfers

Read and create transfers in Brex from any Tray.ai workflow. The Brex API covers calls such as list transfers and get a transfer.

- List transfers
- Get a transfer
- Create a transfer

### Departments

Read, create, update, and delete departments in Brex from any Tray.ai workflow. The Brex API covers calls such as list departments and create a department.

- List departments
- Create a department
- Update a department

## Challenges Tray.ai solves

### Keeping Brex credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Brex credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Brex API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Brex API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Brex?

Yes. Tray.ai connects to Brex through the HTTP Connector, which calls the Brex API directly. Any call the Brex API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Brex?

The Brex API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Brex connector?

Brex runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Brex connector from the Brex API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/