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