Use OAuth to obtain a token with the oauth.readonly scope, then store the access token securely for subsequent API calls to fetch installed locations and manage SaaS subscriptions.
4Degrees authenticates through the linked SaaS API connection. Ensure you grant the necessary permissions and validate tokens before making changes to locations or subscriptions.
GET /oauth/installedLocations; oauth.write; POST /oauth/locationToken; saas/location.write; PUT /update-saas-subscription/:locationId; POST /enable-saas/:locationId
Trigger when a new SaaS location is installed in SaaS API to create or update the corresponding 4Degrees location.
Actions: create or update the corresponding 4Degrees location and sync subscription status.
Core methods: GET /oauth/installedLocations to discover locations and POST /oauth/locationToken to obtain tokens, then map locationId to 4Degrees.
locationId, accessToken, subscriptionStatus
Trigger when a subscription change occurs in SaaS API to update 4Degrees records.
Actions: update 4Degrees subscriptions via saas/location.write or update-subscription endpoints.
PUT /update-saas-subscription/:locationId or POST /enable-saas/:locationId
locationId, subscriptionPlan, renewalDate
Trigger when a new location is created in SaaS API to provision it in 4Degrees.
Actions: create 4Degrees location, set initial settings and enable SaaS features.
POST /enable-saas/:locationId; GET /oauth/installedLocations to verify
locationId, initialSettings, status
No-code setup lets non-developers connect SaaS API to 4Degrees quickly, reducing deployment time.
Drag-and-drop workflows and prebuilt triggers enable rapid automation without writing code.
Automatic data synchronization keeps locations and subscriptions aligned across systems.
Key concepts covered here include OAuth 2.0, API endpoints, tokens, locations, and subscriptions as they relate to the SaaS API and 4Degrees integration.
A token-based authorization framework that lets apps access user data with user consent, without sharing passwords.
A scoped token that grants access to a specific SaaS location for API operations.
The subset of permissions granted by an OAuth token, such as oauth.readonly.
The plan and features assigned to a SaaS location, affecting access and billing.
Automatically provision new SaaS API locations in 4Degrees when a location is created in SaaS API.
Automatically push subscription changes to a centralized dashboard for visibility.
Set up periodic checks to ensure data parity and alert on mismatches.
Create an OAuth app and request scopes like oauth.readonly, then authorize the connection.
Add core endpoints to your workflow and map location data to 4Degrees.
Run tests, verify data flow, and deploy to production.
The SaaS API is the GHL API name used to connect your SaaS platform to 4Degrees through GHL. It exposes endpoints for authentication, location management, and subscription updates. You can configure authentication using OAuth to securely access location data. Once connected, you can automate data flow between systems without custom coding.
No code is required to connect SaaS API to 4Degrees; the integration provides triggers, actions, and prebuilt workflows. Depending on the complexity of your use case, simple point-and-click configurations may be enough, or you can extend with minimal scripting if needed.
This setup uses core endpoints such as GET /oauth/installedLocations, POST /oauth/locationToken, saas/location.write, and PUT /update-saas-subscription/:locationId to manage locations and subscriptions between SaaS API and 4Degrees. Endpoints are mapped to corresponding actions in your workflow.
A location token is a scoped credential that grants access to a particular SaaS location for API operations. It helps ensure calls affect the correct location and keeps access restricted to the intended resource.
Test the connection by running a dry-run in your integration tool, verifying that a location from SaaS API appears in 4Degrees, and that subscription changes propagate correctly. Check token validity and endpoint permissions during the test.
Subscriptions and locations synchronize through defined endpoints that update 4Degrees when SaaS data changes. Regular polling or event-driven triggers ensure both systems reflect the same state.
API documentation for the SaaS API and integration details can be found in the official SaaS API docs and the GHL developer portal. For support, contact your integration administrator or the support channels provided by SaaS API and 4Degrees.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
