Skip to main content

Overview

Pre-built tooling

ToolsStatus
Pre-built authorization (OAuth)
Credentials auto-refresh
Auth parameters validation
Pre-built authorization UI
Custom authorization UI
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
Contribute useful links by editing this page

API gotchas

  • The OAuth1 and OAuth2 APIs give access to different data. Both are supported by Nango.
  • For the OAuth 2 API: To get your client_id and client_secret you need to generate a “user authentication” within your app in the Twitter development portal.
  • Twitter also offers a client credentials token that authorizes as app instead of a user. This is listed under twitter-oauth2-cc. For more details check twitter client credentials flow
Contribute API gotchas by editing this page
I