Authenticate to SaaS API using OAuth with scoped access to installations, locations, and subscriptions, then securely store your tokens for recurring calls.
Grant 46elks the required permissions to access SaaS API endpoints and manage locations, tokens, and subscriptions securely.
GET /oauth/installedLocations; oauth.write; POST /oauth/locationToken; saas/location.write; PUT /update-saas-subscription/:locationId; POST /enable-saas/:locationId
Trigger: user connects SaaS API to 46elks and authorizes access.
Actions: query installed locations (GET /oauth/installedLocations) and request a location token (POST /oauth/locationToken).
GET /oauth/installedLocations; POST /oauth/locationToken
Key fields: locationId, locationToken, accessToken
Trigger: need to update a location’s SaaS subscription
Actions: update subscription (PUT /update-saas-subscription/:locationId) and enable SaaS for a location (POST /enable-saas/:locationId).
PUT /update-saas-subscription/:locationId; POST /enable-saas/:locationId
Key fields: locationId, subscriptionId, status
Trigger: syncing location data after changes.
Actions: saas/location.write
saas/location.write
Key fields: locationId, payload
Benefit 1: Build powerful automations without coding.
Benefit 2: Centralized management of locations and subscriptions.
Benefit 3: Real-time data syncing across systems.
Key elements and processes: OAuth authentication, endpoints, tokens, location data, and subscription management.
OAuth is a standard for granting access to user data without sharing credentials, enabling secure delegated access.
An API URL that performs a specific function and returns data or performs an action.
A set of endpoints and methods that allow programs to communicate and exchange data.
A credential used to authorize API calls, such as an access token or a location token.
Auto-create locations in SaaS API and provision tokens when a new 46elks account is added.
Push subscription changes from SaaS API to 46elks instantly via API calls.
Enrich 46elks data with SaaS API metadata for richer automation.
Authorize SaaS API access for 46elks in your GHL account.
Install the SaaS app and approve required scopes.
Configure endpoints and verify connectivity with test calls.
No coding is required for a basic connection. The SaaS API provides endpoints you can call from within GHL to install locations, obtain tokens, and manage subscriptions. Use the provided UI or automation rules to set up triggers and actions. For more complex flows, you can still leverage no-code logic to map fields and route data between SaaS API and 46elks.
At minimum, call GET /oauth/installedLocations to view locations and POST /oauth/locationToken to retrieve a location token. For subscription management, PUT /update-saas-subscription/:locationId and POST /enable-saas/:locationId are commonly used to modify and enable services.
Location tokens are issued per location after OAuth authorization. Use POST /oauth/locationToken to generate a token for a given locationId and store it securely.
Yes. Automations can trigger subscription updates and onboarding using the SaaS API endpoints, without writing code, by wiring triggers to actions in GHL.
Access tokens authorize API calls for your app, while location tokens grant access to data for a specific location. They serve different scopes and should be stored securely and rotated as needed.
Test calls in a sandbox environment first. Verify responses, monitor logs on both SaaS API and 46elks, and ensure tokens and permissions are correctly scoped.
Refer to the SaaS API rate limits and quotas in the docs. Build retry logic and exponential backoff into your automations to handle limits gracefully.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
