Learn how SaaS API uses OAuth to authorize the Zapier App Connector and access installed locations and tokens
Discovery and consent flow for Zapier App Connector to request access to your SaaS API resources
GET /oauth/installedLocations; POST /oauth/locationToken; saas/location.write; PUT /update-saas-subscription/:locationId; POST /enable-saas/:locationId
Trigger: When a user installs SaaS API, request a location token
Actions: retrieve installedLocations, generate a location token, and store the token
Endpoints used: GET /oauth/installedLocations and POST /oauth/locationToken
locationId, token, locationName
Trigger: location subscription updated in SaaS API
Actions: PUT /update-saas-subscription/:locationId, POST /enable-saas/:locationId
PUT /update-saas-subscription/:locationId; POST /enable-saas/:locationId
locationId, subscriptionId, status
Trigger: new scopes or permissions required
Actions: manage scopes token refresh and audit logs
OAuth scope adjustments and token refresh calls as needed
scope, token, expires
No code setup that lets you connect and automate in minutes
Secure OAuth based access that does not require sharing credentials
End to end automation across apps without custom development
Elements and processes include endpoints tokens locations and subscriptions used to connect SaaS API to Zapier
OAuth is an open standard for access delegation used by SaaS API to securely authorize apps without sharing credentials
An API endpoint is a specific URL that performs a function in the SaaS API
A location represents an instance where SaaS API is installed for a customer
Subscription refers to the plan or service activation for a given location
Onboard new customers by provisioning locations via OAuth and triggering follow up tasks in Zapier
Keep teams informed by syncing subscription changes and posting alerts to Slack or email
Create workflows that react to new or updated locations
Grant access to Zapier App Connector to read SaaS API data
Generate a location token to securely access location data
Enable and manage subscriptions for each installed location
The SaaS API is a scalable API that exposes location data and subscription controls. It lets the Zapier App Connector access your data securely without sharing user credentials. The integration is designed to be no code friendly, so you can automate tasks without writing code.
The Zapier App Connector acts as a bridge between the SaaS API and your automation workflows. It uses OAuth to obtain tokens and handles requests to endpoints. With clear consent flows, you can authorize just the permissions needed and manage tokens automatically.
Permissions depend on the actions you want. Read access is used to fetch installed locations while write permissions are needed to update subscriptions. Use the principle of least privilege. Always review and audit granted permissions to minimize risk.
Location tokens are generated after you authorize access. The token is used to authenticate requests for a specific location. Tokens may expire and require refresh via the token endpoint.
Yes you can manage subscriptions via Zapier. Use the update subscription endpoints and enable saas for locations. Automations can adjust subscription settings from your workflows. This eliminates manual updates and ensures consistency across systems.
Security considerations include using OAuth scopes token rotation and secure storage of tokens. Do not hardcode credentials in apps and monitor access with logs. Regularly rotate tokens and use least privileged scopes.
Endpoint details are available in the SaaS API reference. You can find base URL paths required parameters and response schemas for each operation. Bookmark the endpoints you plan to use and test them in a sandbox environment.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
