nango

on. API catalog: https://www.nango.dev/api-integrations Docs: https://docs.nango.dev Repo: https://github.com/NangoHQ/nango We would love to hear what you think! [0]: https://news.ycombinator.com/item?id=34693233

Detects expired/broken access tokens - Very detailed logs for quick & easy debugging More than 300 companies use Nango Auth in production for their product integrations: From fast-growing AI startups (Respell, Beam, Levity) to established SaaS players (Typeform, Semgrep, Electric) and even public companies. We also run a Slack Community[3] with 2,000+ engineers building product integrations. Nango Auth is a part of Nango[4], our source-available product integrations platform. While Nango itself is a paid product, our auth product (Nango Auth) is free for unlimited use, forever. It’s our small way of giving back to the community. You can either self-host Nango Auth or use our free cloud option. We hope Nango Auth can be helpful for your next integration, and look forward to your feedback! Demo video: https://www.loom.com/share/e704192eb5ba42479803135db1ceccd8 GitHub Repo: https://github.com/NangoHQ/nango Landing page: https://www.nango.dev/auth [0]: https://www.nango.dev/blog/why-is-oauth-still-hard [1]: https://news.ycombinator.com/item?id=34693233 [2]: https://docs.nango.dev/integrations/overview [3]: https://nango.dev/slack [4]: https://www.nango.dev

er-specific configurations, like custom field mappings. We handle (O)Auth and run your integrations reliably in production. Under the hood, your integrations run as typescript “lambdas” on Nango. A typical integration has 3-5 lambdas of 20-50 lines of code each. These lambdas live inside your git repo, are version-controlled with the rest of your app, and get deployed to Nango with a CLI (https://docs.nango.dev/understand/core-concepts). Our runtime has a built-in scheduler for continuous background syncs, monitoring to know if your integrations run as expected, detailed logging of everything that happens in Nango, and pre-built infrastructure to deal with (O)auth, retries, rate-limit handling, webhook floods, data caching, de-duplication, etc. More here: https://docs.nango.dev/understand/architecture We have found that ChatGPT and Copilot let you build integrations on Nango very fast without having to learn each API’s intricacies. LLMs are great at figuring out which endpoint to use, what parameters it takes, etc. Paired with our runtime, this lets you build complex, high-scale integrations in hours instead of weeks. We’ve put a ton of effort into dealing with API complexities, so you don’t have to. Even integrations that looked simple at first ended up forcing us to extend our infra to deal with their quirks and gotchas. For example, we had to figure out 100+ different OAuth implementations (see https://www.nango.dev/blog/why-is-oauth-still-hard and https://news.ycombinator.com/item?id=35713518). We had to deal with a half-dozen non-standard auth methods (Github apps, Stripe apps, Netsuite, etc.), expiring webhooks, ways to deal with data dependencies, weird pagination methods, API keys that change with every API call, dozens of different ways to register for webhooks, etc. It’s a constantly moving target, but it is a challenge we have come to love, and we think the approach makes sense: we specialize in finicky details that vary from API to API—you specialize in making your product great and offering more integrations to your users. Last but not least, Nango is open source (https://github.com/NangoHQ/nango) under the ELv2 license (allows most use cases, except for direct copy-cats). Anybody can contribute new APIs & share their integration templates with the community. The fastest way to see Nango in action is with our interactive demo here (no signup required): https://app.nango.dev/hn-demo Or take a look at our docs: https://docs.nango.dev We would love to hear your feedback and look forward to the comments!

.). Our platform has two layers: (1) An API-agnostic infrastructure built with Temporal and Postgres, and (2) lambda function-like integrations written in typescript by any developer. Integrations are rarely more than 50 lines of code (here is an example: https://bit.ly/nango-example), thanks to the developer tooling we’ve built in: authentication, pagination, retries, change detection, rate-limit handling, monitoring, Slack alerts, etc. We have pre-built integration templates you can clone and extend—or you can build entirely custom integrations. Your integrations live in your repo and are tested and deployed to Nango with a CLI. In your product, you use a single API to interact with all your integrations. This lets you easily grow the available integrations with minimal code changes in your product. As a community-driven project, anybody can contribute integration templates and APIs to the platform. In fact, more than 30% of the APIs we support today have been contributed by our community. Nango grew out of a “universal OAuth” project called Pizzly and powers the integrations of 100+ SaaS products today. We have an active community of 800+ developers (https://nango.dev/slack). All auth-related features are free forever, and we monetize with sync-related features. The entire code base and all integrations are source-available: https://github.com/NangoHQ/nango. We hope Nango can help connect all SaaS products together and look forward to your feedback!

successful is Okta. [0] - https://github.com/NangoHQ/nango [1] - https://merge.dev/

the OAuth dance, token storage & refreshes for you. It works with any language, API or framework. It is easily self-hostable for free, or as a cloud service if you want to avoid the burden of securing tokens yourself (that’s how we pay the bills). To get started we recommend you take a look at our Quickstart on the GitHub repo: https://github.com/NangoHQ/nango We currently support 40+ popular APIs. Adding a new one is as simple as updating a YAML file, so anybody can contribute one. In the coming weeks we plan to add a dashboard, a proxy to authorise requests, monitoring and more APIs. One thing we learned from talking to other engineers about OAuth is that everybody has their own horror stories: What was the hardest OAuth API you ever used? What made it so difficult? We look forward to your stories and your feedback on Nango! Repo: https://github.com/NangoHQ/nango // Website: https://www.nango.dev