Integrations / Brex
Brex
Brex corporate cards, expenses, transactions, and reimbursements. Webhook-driven for real-time receipt filing and policy enforcement.
What Telara does
Capability matrix
Before you connect
Prerequisites
Vendor setup
Get the credential
Permissions Telara requests
- expenses:readOAuth 2.0
- expenses:writeOAuth 2.0
- transactions:readOAuth 2.0
- team:readOAuth 2.0
- budgets:readOAuth 2.0
In Telara
Connect in Telara
Brex API user token from Settings > Developer > User Tokens. Scopes required vary by endpoint: expenses:read, expenses:write, transactions:read, team:read, budgets:read.
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
- API key
Brex OAuth for partner apps. Use api_key for single-tenant internal automation.
In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Expense | Partial — not every record the vendor holds is synced |
| Transaction | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Expense | Up to 1 hour | Removed records disappear on the next full sync |
| Transaction | Up to 1 hour | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.
Excluded from semantic search: Expense, Transaction.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty