β Authorization
β Read & write data
Tools | Status |
---|---|
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 | β |
β Observability & data quality
Tools | Status |
---|---|
HTTP request logging | β |
End-to-type type safety | β |
Data runtime validation | β |
OpenTelemetry export | β |
Slack alerts on errors | β |
Integration status API | β |
β Customization
Tools | Status |
---|---|
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-Requisites | Status | Comment |
---|---|---|
Paid dev account | β | |
Paid test account | β | |
Partnership | β | |
App review | β | |
Security audit | β |
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
.
offline_access
to get a refresh token (access tokens expire after 1h).