Authenticate requests using your API key or OAuth credentials. Store tokens securely and rotate keys regularly.
Connect Abyssale by authorizing OAuth scopes for calendars write access and ensuring the app can read calendar data.
POST /calendars/ create a new calendar; PUT /calendars/:calendarId update an existing calendar; DELETE /calendars/:calendarId remove a calendar; calendars.readonly list calendars; GET /calendars/ list all calendars; GET /calendars/:calendarId fetch a specific calendar; GET /calendars/:calendarId/free-slots check availability; calendars.groups.readonly list calendar groups; GET /calendars/groups list groups; calendars/groups.write create a group; POST /calendars/groups/validate-slug validate a group slug; DELETE /calendars/groups/:groupId delete a group; PUT /calendars/groups/:groupId update a group; PUT /calendars/groups/:groupId/status change a group status; calendars/resources.readonly list resources; GET /calendars/resources/:resourceType fetch resource types
Trigger when a new Abyssale campaign is created to generate a corresponding calendar in Calendars API.
Actions to perform include POST /calendars to create the calendar and POST /calendars/groups to organize it into groups.
POST /calendars/ and POST /calendars/groups
key fields like name, timezone, owner, and groupId for mapping
Trigger when Abyssale updates availability that should reflect on calendars.
Actions: GET /calendars, GET /calendars/:calendarId, GET /calendars/:calendarId/free-slots
GET endpoints for syncing
id, slots, availability, and calendarId
Trigger when permissions change or groups are updated in Abyssale.
PUT /calendars/groups/:groupId, DELETE /calendars/groups/:groupId, PUT /calendars/groups/:groupId/status
PUT /calendars/groups/:groupId, DELETE /calendars/groups/:groupId, PUT /calendars/groups/:groupId/status
groupId, slug, status, permissions
Automate event creation and updates without custom scripting.
Keep calendars in sync across apps in real time.
Scale calendar management for teams with group based access.
Understand calendars endpoints, resources, groups, and the data flow between Abyssale and Calendars API.
A container of events and availability used to coordinate scheduling.
A specific URL path that performs a defined operation on the API.
A data type exposed by the API such as calendars, groups, or resources.
Process of proving identity to gain access to API calls, typically via OAuth tokens or API keys.
When a new Abyssale campaign is created, automatically generate a calendar entry in Calendars API with the campaign timeline.
Publish availability to Abyssale campaigns so teammates can book slots.
Generate shareable booking links from calendars when sending Abyssale emails.
In GHL, create an API key with calendars.write scope and note the client ID.
Add redirect URL and set up required scopes for calendars.readonly and calendars.write.
Use sandbox data to verify endpoints and error handling.
Authenticate by including your API key or OAuth token in the request header. Use the calendars.write scope for creating and updating calendars. Rotate keys regularly and store credentials securely. If you encounter token expiration, refresh tokens or generate a new key as required by the chosen authentication method.
The core endpoints include creating, updating, listing, and deleting calendars as well as managing calendar groups and retrieving resources. You can also check availability via free slots and validate group slugs before creation. Refer to the endpoint list for full details and usage examples.
Yes. You can associate Abyssale campaigns with specific calendars or groups to coordinate events and availability across multiple calendars. Use grouping and permissions to manage who can view or modify calendars.
Basic integration can be achieved without code using native connectors or automation tools. More complex workflows may require light scripting to map data fields between Abyssale and Calendars API.
Rate limits vary by plan. Plan for bursts during campaigns and implement retries with backoff. Monitor usage in your GHL dashboard and adjust token lifetimes accordingly.
Token expiration is handled by your OAuth provider or by regenerating API keys. Build logic to refresh tokens automatically or prompt for re-authentication when needed.
API documentation is available in your developer portal and the GHL integration section. It includes endpoint references, parameter details, and example requests.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
