Authenticate with OAuth 2.0 via the Calendars API. In the GHL developer portal, create a client and grant calendars.write scope to allow Acadimiat to create and update calendars.
Acadimiat uses OAuth tokens issued by GHL to access your calendars. Store tokens securely, refresh before expiry, and rotate credentials as needed.
Key endpoints include POST /calendars/ to create calendars, GET /calendars/ to list, GET /calendars/:calendarId, PUT /calendars/:calendarId, DELETE /calendars/:calendarId, and GET /calendars/:calendarId/free-slots for availability.
Trigger: Acadimiat creates a calendar and a matching calendar is created in Calendars API.
Actions: create, update, delete calendars; sync names, time zones, and descriptions.
Example: POST /calendars/ to create; PUT /calendars/:calendarId to update; DELETE /calendars/:calendarId to remove.
Key fields: calendarId, name, timeZone, color, description.
Trigger: fetch free-slots to show available times in Acadimiat.
Actions: GET /calendars, GET /calendars/:calendarId, GET /calendars/:calendarId/free-slots.
Examples: GET /calendars/ and GET /calendars/:calendarId/free-slots.
Key fields: calendarId, freeSlots, availability.
Trigger: updates to calendar groups propagate to Acadimiat.
Actions: POST /calendars/groups, PUT /calendars/groups/:groupId, DELETE /calendars/groups/:groupId, PUT /calendars/groups/:groupId/status.
Examples: POST /calendars/groups, PUT /calendars/groups/:groupId, DELETE /calendars/groups/:groupId, PUT /calendars/groups/:groupId/status.
Key fields: groupId, slug, title, permissions.
Faster setup with no server code required; connect in minutes.
Automations run in the cloud, using webhooks and scheduled syncs.
Scale across multiple calendars and teams without custom development.
Key elements include calendars, groups, endpoints, authentication flows, and data fields used in the integration.
A calendar is a container for events and availability within both Acadimiat and the Calendars API.
An event represents a scheduled item on a calendar with start and end times.
A group defines who can view or modify a set of calendars.
A URL path that performs an action on a resource in the API.
Trigger reminders from Acadimiat when events are near to reduce no-shows.
Show live availability in Acadimiat by syncing free-slots from Calendars API.
Control who can view or edit calendars via groups integration.
Register a new app in the GHL developer portal and capture clientId and clientSecret for Calendars API.
Add calendars.write scope and set the redirect URL to Acadimiat.
Use test calls like POST /calendars/ and GET /calendars/ to verify connectivity and data flow.
Authentication relies on OAuth 2.0. You obtain a clientId and clientSecret from the GHL developer portal and request an access token with the calendars.write scope. Use the access token to authorize Acadimiat’s API calls to Calendars API. Refresh tokens as needed per the OAuth flow. Securely store credentials and rotate them when required.
The core endpoints cover calendar CRUD operations (POST /calendars/, GET /calendars/, GET /calendars/:calendarId, PUT /calendars/:calendarId, DELETE /calendars/:calendarId) and availability (GET /calendars/:calendarId/free-slots). You can also manage groups (POST /calendars/groups, PUT /calendars/groups/:groupId, DELETE /calendars/groups/:groupId) and broader read access (GET /calendars/groups).
You can start with no-code app connectors within Acadimiat to map calendars and events. For deeper customization, you can call the REST endpoints directly from your automation flows. Both approaches are supported.
Expect standard API rate limits; implement exponential backoff for 429 responses and handle 4xx/5xx errors gracefully. Use the error details returned in responses to adjust retries and user messaging.
Yes. The calendars/groups endpoints let you create, update, delete groups and assign permissions. This helps you control who can view or modify calendars across teams.
Webhooks are supported for real-time updates where available. You can subscribe to events like calendar changes or group updates and push those updates into Acadimiat as they occur.
Credentials are generated in the GHL developer portal. Create your app, note the clientId and clientSecret, and configure redirect URLs. Use these in the OAuth flow to obtain access tokens for Acadimiat.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
