Use OAuth 2.0 tokens or a dedicated API key to securely authenticate requests to Calendars API from ablefy. Keep credentials in a secure vault and rotate them regularly.
Configure ablefy to present the credentials when calling Calendars API. Create an OAuth client in ablefy and grant the calendars.write scope.
– POST /calendars/ — Create a calendar\n- PUT /calendars/:calendarId — Update a calendar\n- DELETE /calendars/:calendarId — Delete a calendar\n- GET /calendars/ — List calendars\n- GET /calendars/:calendarId — Get a calendar\n- GET /calendars/:calendarId/free-slots — Check availability\n- GET /calendars/groups — List groups\n- POST /calendars/groups — Create groups\n- POST /calendars/groups/validate-slug — Validate slug\n- PUT /calendars/groups/:groupId — Update group\n- DELETE /calendars/groups/:groupId — Delete group\n- PUT /calendars/groups/:groupId/status — Update group status\n- GET /calendars/resources/:resourceType — Get resources
Trigger: a new calendar is created in Calendars API
Actions: create corresponding calendar in ablefy, sync attributes, and set up default groups
POST /calendars/
Required fields: name, time_zone, color
Trigger: a user requests available slots
Actions: fetch free-slots and return to ablefy; do not modify calendars
GET /calendars/:calendarId/free-slots
Required: calendarId; date range and duration are optional
Trigger: group or resource changes
Actions: create/update groups and assign resources; synchronize with ablefy
Example: POST /calendars/groups and PUT /calendars/groups/:groupId
Required fields: slug, name, calendarId for updates; status optional
Rapid setup: connect in minutes without writing code
Real-time sync: calendars, groups, and availability stay up-to-date
Scalability: manage multiple calendars and resources across teams
This section covers the core elements: calendars, groups, resources, and the authentication flow, plus the processes to authorize, fetch, create, update, and delete.
A specific URL and method used to perform an action against the Calendars API.
An object representing a calendar that can be created, fetched, or modified.
Authorization framework for secure access to APIs without sharing credentials.
A limit on how many requests can be made in a given time window.
Automatically route new appointments to the right calendar in ablefy based on rules.
Show real-time free-slots inside ablefy and allow users to book instantly.
Manage multiple calendars and groups at scale with bulk endpoints.
Register your Calendars API credentials and grant the calendars.write scope from ablefy.
Map Calendars API endpoints to ablefy actions and set data mappings for calendars, groups, and resources.
Run tests to ensure creation, retrieval, and slot fetching work as expected; monitor logs and adjust mappings.
You can authenticate using an API key or OAuth 2.0 token. In most setups, OAuth is recommended for secure, token-based access. Store credentials securely and configure them in ablefy; then authorize the calendars.write scope for access to the Calendars API.
To create a calendar, call POST /calendars/ with required fields such as name and time_zone. Then fetch the list with GET /calendars/ to confirm creation.
Use GET /calendars/:calendarId/free-slots to retrieve available times. You can filter by date range and duration. Integrate the response into ablefy’s booking UI or workflow.
Yes. Use POST /calendars/groups to create groups and PUT /calendars/groups/:groupId to update them. Sync changes by wiring webhooks or periodic polling in ablefy.
The Calendars API enforces rate limits; expect a cap on requests per minute. Check response headers for current limits. Plan calls accordingly and implement exponential backoff in retries.
If a request fails, verify credentials, scopes, and endpoint availability. Review ablefy logs. Retry with backoff and ensure correct IDs (calendarId, groupId) are used.
Most GHL accounts can connect; some require higher plans or API access enablement. If you cannot connect, contact support to confirm availability for your account.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
