OAuth scopes define which Zapier resources your application can access. Request only the scopes required for the endpoints or flows your application uses. Endpoint-specific scope requirements are listed on each API reference page.
When requesting more than one scope in an OAuth flow or token exchange, pass scopes as a space-separated string.
Zapier API scopes
Additional scopes
Choosing Zap read scopes
Use the narrowest Zap read scope that supports your use case:
- Use
zap when you only need Zap workflows that use your integration.
- Use
zap:all when you need all Zap workflows owned by the authenticated user.
- Use
zap:account:all when you need Zap workflows the authenticated user can access across their account, including shared workflows.
The scope you choose also controls the inputs field on each step returned by /v2/zaps. With zap, inputs is populated only for steps that use your integration and is null for every other step. With zap:all or zap:account:all, inputs is populated for every step. You do not need both of these scopes; they differ only in which Zap workflows are returned. Last modified on October 22, 2026
