Authenticate with the Calendars API using OAuth2 tokens and the calendars.write scope. This enables creating, updating and managing calendars and events from AccessAlly.
Authorize AccessAlly to access GHL calendars by configuring an API token in the app settings. Store tokens securely and rotate them as recommended.
Key endpoints include POST /calendars, PUT /calendars/:calendarId, DELETE /calendars/:calendarId, calendars.readonly, GET /calendars/, GET /calendars/:calendarId, GET /calendars/:calendarId/free-slots, calendars/groups.readonly, GET /calendars/groups, POST /calendars/groups, POST /calendars/groups/validate-slug, DELETE /calendars/groups/:groupId, PUT /calendars/groups/:groupId, PUT /calendars/groups/:groupId/status, calendars/resources.readonly, GET /calendars/resources/:resourceType.
Trigger when a new calendar is created or updated in AccessAlly to sync with GHL calendars.
Actions: POST /calendars, PUT /calendars/:calendarId, GET /calendars/
POST /calendars/ and PUT /calendars/:calendarId
calendarName, timeZone, color, reminders
Trigger on group changes in AccessAlly to update GHL calendar groups.
Actions: POST /calendars/groups, PUT /calendars/groups/:groupId, DELETE /calendars/groups/:groupId, GET /calendars/groups
POST /calendars/groups and PUT /calendars/groups/:groupId
groupName, slug, status
Trigger to fetch available slots using the free-slots endpoint.
Actions: GET /calendars, GET /calendars/:calendarId/free-slots
GET /calendars/:calendarId/free-slots
calendarId, startDate, endDate
No coding required to connect AccessAlly with Calendars API through GHL.
Automate scheduling workflows without developers and handoffs.
Rapid deployment with ready made endpoints and comprehensive docs.
This glossary covers API terms used in this guide including endpoints, resources, and authentication.
A set of rules and endpoints that let apps talk to each other over HTTP.
A specific URL path and HTTP method used to perform an operation in an API.
An object exposed by an API such as calendars, groups or slots that can be read or modified.
A standard protocol for authorizing access to an API without sharing user credentials.
Set up a workflow where new events in AccessAlly trigger calendar creation and updates in GHL.
Link user groups in AccessAlly to calendar visibility and access control in GHL.
Use the free-slots endpoint to suggest times to clients directly from AccessAlly.
Obtain an API token for Calendars API and enter credentials in AccessAlly settings.
Define field mappings for calendar names, groups and slots to sync between systems.
Run tests, verify data sync, monitor logs and enable automation.
No coding is required to connect AccessAlly with Calendars API through GHL. The visual setup lets you enable the integration, map fields and configure triggers without writing code. You can use prebuilt actions for common tasks or customize with webhooks if your workflow needs extra logic. If you require advanced automation, you can extend the setup with additional API calls and conditional steps in AccessAlly workflows.
The core permission needed is the calendars.write scope which allows creating, updating and deleting calendars and events. You may also rely on calendars.readonly for read access as needed. Always apply the principle of least privilege and restrict access to trusted API tokens. In addition, consider enabling group level permissions if you plan to manage access at the calendar group level.
Authentication is done via API tokens and OAuth2 where required. Start by obtaining a token in the GHL developer console and then configure it in AccessAlly. Rotate tokens regularly and store them securely. For user agents and automated tests, use sandbox credentials when available and monitor token scopes to ensure they remain aligned with your use case.
Yes, you can fetch available time slots using GET /calendars/:calendarId/free-slots. Provide date ranges or time zones to tailor the results. This helps you present accurate options to clients in AccessAlly. Combine free slots data with AccessAlly triggers to automate scheduling and reduce back-and-forth with clients.
API documentation is available in the GHL developer portal and the built in API reference in AccessAlly. Look for the Calendars API section to review endpoints, examples and authentication details. If you need more hands on guidance, reach out to support or consult the example workflows provided in the integration setup.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
