Skip to main content
App Authentications let Zapier connect to an external app on a user’s behalf. They represent the credentials (such as OAuth tokens, API keys, or Basic Authentication details) that Zapier securely stores and uses to access another service through its API.
App Authentications are a different concept than authenticating to the Powered By Zapier API.
If you would like information on how to authenticate to our API, please visit our API Authentication documentation.

​
What App Authentications Do

When a user connects their account to an app through Zapier, an App Authentication is created. This stored connection allows Zapier to make authorized requests to the external app without requiring the user to re-enter credentials each time. For example, when a user connects Google Sheets to Zapier, Zapier creates and stores that authentication so future Zap runs can read and write spreadsheet data as needed. The same applies whether the authentication method is OAuth, API key, or username and password.

​
Why They Matter

App Authentications are fundamental to how Zaps run. Each step in a Zap that interacts with an external service needs a valid authentication to perform actions or fetch data. Without it, Zapier cannot communicate with that app’s API on behalf of the user. Developers can manage these authentications through the Powered by Zapier API by retrieving existing connections, adding new ones, or helping users choose which account to use in a workflow.
Once you understand the basics, explore these references to see how App Authentications are created and managed:
⌘I