Universal proxy for 1,000+ APIs
Make authenticated requests to 1,000+ APIs through one endpoint. Nango handles auth, headers, and provider quirks, so tokens never touch your code.
Full API access, no abstraction
Call each provider's native endpoints exactly as their docs describe — no wrapper, no unified schema in between.
Provider quirks, handled
Define only the endpoint and body, and let Nango handle the provider's base URL, headers, and auth placement, retries, and rate limits.
Credentials never leave Nango
Provider tokens stay encrypted inside Nango and are injected at request time — never passing through your code or your repo.
Every call logged
Every proxied request is captured in Nango's logs with status, latency, and headers — one place to debug and audit all your external API traffic.
Enterprise-grade security & scale
Granular access
RBAC, per-user API scopes
Encrypted
At rest & in transit encryption
Self-hostable
Deploy in your environment
99.9% uptime
All incidents reported on our status page
1M+ integrations
Proven at real-world scale
Open-source
Inspectable infrastructure
Compliance
SOC 2, GDPR & HIPAA
Observability
Detailed traces, export with OTel
Support
From Nango engineers
FAQ
Negligible. The proxy typically adds around 100ms or less to a request.
We add new APIs quickly on request, usually within days. You can also add it yourself, since Nango is open source. Docs (opens in a new tab)
No. You call Nango with a connection ID; Nango attaches the credentials and forwards the request. Tokens stay encrypted in Nango. Docs (opens in a new tab)
You set a retry count and Nango retries failures and 429s with exponential backoff, respecting provider rate-limit headers when they exist. Docs (opens in a new tab)
Yes, they share the same connections, credentials and logs. Most teams use syncs for continuous data, actions for reusable operations and agent tools, and the proxy for everything else.
No. For proxy requests, no data passes through or is stored at Nango. Logs keep only the method, URL, status, latency, and headers, never request or response bodies. Docs (opens in a new tab)
Yes. The API returns fresh credentials on demand, and many teams use Nango for auth only. Docs (opens in a new tab)
There's no per-request charge. Pricing is based on connections, compute time, and data transfer; proxy traffic counts toward data transfer. Pricing
There's no predefined list of endpoints on Nango's side. The proxy lets you call any endpoint of a supported API, so when a provider ships a new endpoint you can use it through Nango from day one. If the API itself isn't supported yet, we'll add it on request. Docs (opens in a new tab)
On Nango Cloud, hosted on AWS in the US. If data has to stay in a specific region, the Enterprise plan can run Nango in your own cloud (BYOC): a dedicated Nango deployment inside your AWS, GCP, or Azure account, so requests and data never leave your infrastructure. Pricing
There's a generous 5 MB limit per response. For larger datasets, use syncs, which fetch and paginate the data for you. Docs (opens in a new tab)
Make your first authenticated API call in minutes.
Free to start, no credit card.