The SaaS API uses OAuth 2.0 with the scope oauth.readonly by default. You will authorize access to installed locations and tokens so ablefy can read location data and perform actions as needed.
In ablefy you connect the SaaS API by linking your SaaS API account. After you grant access, ablefy will store tokens and request endpoints on your behalf.
Endpoint1 GET /oauth/installedLocations; Endpoint2 oauth.write; Endpoint3 POST /oauth/locationToken; Endpoint4 saas/location.write; Endpoint5 PUT /update-saas-subscription/:locationId; Endpoint6 POST /enable-saas/:locationId; Additional endpoints available as needed.
Trigger: user authorizes SaaS API and grants access to a location, then ablefy exchanges a location token.
Actions: read installedLocations, exchange a location token, and store locationId for future updates.
Methods used: GET /oauth/installedLocations and POST /oauth/locationToken
Key fields: locationId and token associated with the installed location.
Trigger: SaaS subscription changes trigger an update in GHL via ablefy.
Actions: call update subscription endpoint with locationId to reflect new plan.
PUT /update-saas-subscription/:locationId
Key fields: locationId, subscriptionPlan, renewalDate
Trigger: enabling SaaS for a location from ablefy
Actions: enable SaaS for a location via POST /enable-saas/:locationId
POST /enable-saas/:locationId
Key fields: locationId
No coding needed. Set up once and data flows automatically between systems.
Automations reduce manual work by syncing location data and subscriptions.
Scalability across many locations with minimal setup and maintenance.
This section covers OAuth, tokens, endpoints and the processes used to connect and manage locations, subscriptions and data flows.
OAuth is a standard for delegated authorization used to grant apps access without sharing passwords.
An API endpoint is a URL that performs a specific action in an API.
A location is a distinct instance where a SaaS subscription is installed and managed.
A subscription defines the chosen plan and features for a given location.
Set up welcome flows that create a location in SaaS API and subscribe it to a plan automatically.
Send location based metrics back to your CRM and trigger alerts when thresholds are reached.
Automate renewal reminders for each location to reduce churn.
In GHL, create an app for the SaaS API and obtain a client ID and client secret.
Set the scope oauth.readonly to begin and upgrade to oauth.write for write actions.
Test the installedLocations and locationToken flows to verify access and then enable SaaS for locations.
No coding is required to connect Ablefy with the SaaS API through the GHL integration. You configure the app in GHL, authorize access and map fields. If you want more control, you can add simple workflow rules to extend functionality.
Start by using GET /oauth/installedLocations to pull the locations where the SaaS API is installed. Then exchange a location token with POST /oauth/locationToken to authorize actions for a location.
Testing the connection involves verifying token issuance and ensuring you can read location data. Use the location token flow to confirm that ablefy can perform write actions when authorized. Move to live after successful tests.
Yes. You can manage subscriptions per location by using PUT /update-saas-subscription/:locationId with the new subscription data. This enables location specific control without affecting others.
Tokens and permissions are managed within the GHL connected apps area. You can view granted scopes, refresh tokens and revoke access if needed.
Yes, there is a no code option. Many use cases are resolved with built in workflows and triggers. You can still access endpoints if you need advanced customization.
To go live, complete the OAuth connection in GHL, test the endpoints with a sample location, then enable SaaS for production locations using the locationId and enable-saas endpoint.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
