title | sidebarTitle | description |
---|---|---|
Core concepts |
Core concepts |
Learn more about the core concepts of Nango. |
Nango improves the way applications integrate with external APIs by providing a flexible, customizable unified API. Unlike traditional unified APIs that offer a one-size-fits-all solution, Nango empowers you to tailor the interaction between you app and external APIs, ensuring a perfect fit for your specific needs.
-
Integrations: The configurations that define how to connect to an external API. Each integration represents a separate external service (like Hubspot or Slack) and includes details such as authentication methods and consumable API endpoints.
-
Connections: Connections are instances of integrations for individual users or entities. They store the authentication credentials (like OAuth tokens or API keys) that allow Nango to access the external API on behalf of a specific user or entity.
-
Integration scripts: Integration scripts are the heart of Nango's customization capabilities. They define the logic for how Nango interacts with external APIs, and run on Nango's infrastructure. Scripts are either provided by Nango as templates or implemented by you. There are different types of integration scripts:
-
Generated API reference: Nango automatically generates an API reference specific to your integrations, documenting available endpoints, actions, and sync operations. This dynamic reference, available in the Nango UI, guides developers on utilizing the Nango API to interact with external services.
Nango's architecture can be divided into two main parts:
Use integrations: Your app to Nango
Developers use the unified API provided by Nango to interact with various external APIs. This part offers a streamlined & unified interface for developers, minimizing the integration complexity in your main codebase.
Build integration: Nango to external APIs
Here lies Nango's unique value proposition. Unlike traditional unified APIs, Nango allows you to customize how it interacts with each external API through integration scripts. This means that while the interface from your app to Nango remains unified, the communication from Nango to external APIs offers unprecedented flexibility to meet your specific requirements.
**Questions, problems, feedback?** Please reach out in the [Slack community](https://nango.dev/slack).