Skip to main content

Overview

Pre-built tooling

ToolsStatus
Pre-built authorization (API Key)
Pre-built authorization UI
Custom authorization UI
End-user authorization guide
Expired credentials detection
ToolsStatus
Pre-built integrations🚫 (time to contribute: <48h)
API unification
2-way sync
Webhooks from Nango on data modifications
Real-time webhooks from 3rd-party API🚫 (time to contribute: <48h)
Proxy requests
ToolsStatus
HTTP request logging
End-to-type type safety
Data runtime validation
OpenTelemetry export
Slack alerts on errors
Integration status API
ToolsStatus
Create or customize use-cases
Pre-configured pagination🚫 (time to contribute: <48h)
Pre-configured rate-limit handling🚫 (time to contribute: <48h)
Per-customer configurations

Pre-built integrations

No pre-built integration yet (time to contribute: <48h)
Not seeing the integration you need? Build your own independently.

Access requirements

Pre-RequisitesStatusComment
Paid dev account
Paid test account
Partnership
App review
Security audit

Setup guide

No setup guide yet.
Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
Brex offers both Basic auth API key and OAuth as authentication and Nango implements both. To register an OAuth app, you wil need to register as a brex developer partner. If you are a Brex client–i.e., you have your own Brex account, you can use Basic auth API key.
Contribute useful links by editing this page

API gotchas

  • Include the scope offline_access to get a refresh token (access tokens expire after 1h).
  • Refresh tokens expire after 90 days of non use. Make sure you regularly make an API request as long as you need the connection.
  • Brex offers a staging system to test your apps, you will get access when you register as a partner. Staging details are here
Contribute API gotchas by editing this page

Going further

Connect to Brex (api key)

Guide to connect to Brex (api key) using Connect UI
I