Authorize SaaS API in GHL to read installed locations with oauth.readonly, and request oauth.write for subscription changes. Follow OAuth 2.0 flow to grant permissions.
In 17hats, approve the GHL connector to access your data. You will be redirected to login and grant permissions; no code is required.
1) GET /oauth/installedLocations – retrieves all locations installed for the connected GHL account. 2) oauth.write – OAuth scope to grant write capabilities. 3) POST /oauth/locationToken – generates a token for a specific location. 4) saas/location.write – enables location data write operations. 5) PUT /update-saas-subscription/:locationId – updates a location’s SaaS subscription. 6) POST /enable-saas/:locationId – enables SaaS for a location. 7-17 – not used on this page.
Trigger: a new or updated location in SaaS API requires 17hats to reflect changes.
Actions: create or update location in 17hats; apply subscription changes; map ID fields.
Method path: PUT /update-saas-subscription/:locationId and POST /enable-saas/:locationId
Key fields: locationId, subscriptionId, status
Trigger: a new location is installed and needs a token.
Actions: generate locationToken via POST /oauth/locationToken; store token securely in 17hats.
Method path: POST /oauth/locationToken
Key fields: locationId, token
Trigger: on first connection, fetch installed locations.
Actions: pull installedLocations via GET /oauth/installedLocations; map to 17hats.
Method path: GET /oauth/installedLocations
Key fields: locationId, installedVersion
No-code setup lets you connect SaaS API to 17hats using a visual connector and ready-made endpoints.
Automate location and subscription data flow without writing code, reducing manual data entry.
Fast onboarding and scalable workflows for teams managing multiple locations.
This glossary defines the core terms and processes you’ll see when connecting SaaS API to 17hats, including OAuth, endpoints, locations, and subscriptions.
OAuth 2.0 is an authorization framework that lets apps access user data securely with permission, without sharing passwords.
A location in SaaS API represents a specific site or account to which you apply a subscription and settings.
A subscription defines the plan and services active for a given location within SaaS API.
A token is a temporary credential used to authorize API requests between SaaS API and 17hats.
Create a guided setup flow that walks users through OAuth, location selection, and field mapping with templates.
Provide templates to map SaaS API fields to 17hats data fields with validation.
Send alerts to teams when subscriptions change or a location is enabled, using webhooks.
Begin by granting permissions via OAuth to access locations and subscriptions in SaaS API and 17hats.
Select the locations you want to sync and map fields between SaaS API and 17hats.
Run a test sync, verify data, and enable automation in production.
No coding is required. The GHL connector provides a visual setup and prebuilt endpoints to connect SaaS API to 17hats. Use the wizard to authorize, select locations, and map fields. You can customize mappings later if needed.
Core syncing uses endpoints like GET /oauth/installedLocations, POST /oauth/locationToken, and PUT /update-saas-subscription/:locationId. These enable location and subscription data to flow between SaaS API and 17hats.
Credentials are stored securely by the platform with encryption at rest and in transit. OAuth tokens are refreshed automatically as needed and never exposed in plain text.
Yes. You can map fields such as location name, subscription status, and ID fields. Use templates to ensure data integrity across systems.
Use the test mode and sandbox features to validate a few locations first. Confirm data accuracy before enabling live syncing.
API quotas apply depending on your plan. The integration is designed to handle typical SaaS API usage and can throttle requests to protect systems.
You can view logs in the connector dashboard, search for error messages, and use the troubleshooting guide to resolve common issues.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
