Start with OAuth scopes for installedLocations and locationToken to securely access the SaaS API.
Use Acuity Scheduling credentials or an OAuth token to authorize data flow from SaaS API.
Endpoints used: GET /oauth/installedLocations; POST /oauth/locationToken; saas/location.write; PUT /update-saas-subscription/:locationId; POST /enable-saas/:locationId. Additional endpoints are available as features are enabled.
Trigger: a new SaaS location is created to automatically mirror the location in Acuity Scheduling.
Actions: create or sync the location in Acuity Scheduling, assign a calendar, and mirror settings.
Method path examples: POST /oauth/locationToken to obtain access, or saas/location.write to push location data.
Key fields: locationId, accessToken, refreshToken, calendarId.
Trigger: SaaS subscription updated.
Actions: update the subscription on Acuity Scheduling and adjust availability.
PUT /update-saas-subscription/:locationId
Fields: locationId, subscriptionId, planId, status
Trigger: tokens rotate and sessions stay active.
Actions: refresh tokens with POST /oauth/locationToken and reuse tokens securely.
POST /oauth/locationToken
Fields: clientId, clientSecret, locationId, token
Automate appointment data sync without writing code.
Real-time booking updates keep everyone in sync.
Scalability to manage multiple locations and subscriptions.
A concise glossary of terms used in this integration: OAuth, location, subscription, endpoint, token, and mapping.
OAuth is a token-based authentication standard that lets apps access resources securely without passwords.
A specific URL path that exposes a function in the SaaS API.
A connected SaaS app instance within GHL.
A plan or tier associated with a SaaS account that can be activated for a location.
Auto-create clients in Acuity Scheduling when new SaaS accounts are added.
Update scheduling availability based on subscription tier.
Provide dashboards showing bookings and usage across connected locations.
Grant OAuth access for installedLocations and locationToken scopes.
Link a location in Acuity Scheduling and store tokens.
Turn on SaaS integration for the location and monitor the sync.
The SaaS API is a RESTful interface that lets Acuity Scheduling connect with external apps to manage locations, subscriptions, and tokens. It uses OAuth token based authentication to protect data and grant scoped access.
Authentication uses OAuth with scopes such as oauth.readonly and oauth.write. You will obtain a locationToken and a refresh token to maintain access without reauthenticating.
Core endpoints include installedLocations, locationToken, saas/location.write, update-saas-subscription, and enable-saas. Not every page uses all endpoints; plan according to the workflow.
Data synced includes location data, subscriptions, and basic client information depending on permissions and mappings configured.
All data transfers occur over HTTPS with token based authentication and least privilege scopes to minimize risk.
Yes, you can map and customize fields between the SaaS API and Acuity Scheduling to fit your workflow.
If a token expires, use the refresh token flow to obtain a new access token without re authenticating the user.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
