Authenticate the Calendars API within GHL by using your API key or OAuth credentials, then grant access to calendars and resources needed for Accredible workflows.
Authenticate Accredible Certificates within GHL by securely storing app credentials and using tokens to authorize API calls in workflows.
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, calendars/groups.write, 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 Accredible issues a certificate, automatically create a calendar event in Calendars API.
Actions: POST /calendars/ to create the event, then attach attendees and reminders as needed.
POST /calendars/ with payload including title, start_time, end_time, attendees, description.
title, start_time, end_time, attendees, description, location
Trigger: A user begins scheduling in Accredible Certificates and requests available times.
Actions: GET /calendars/:calendarId/free-slots to present options.
GET /calendars/:calendarId/free-slots
calendarId, date, time_slot, capacity
Trigger: Changes to calendar groups propagate to Accredible workflow assignments.
Actions: POST /calendars/groups, PUT /calendars/groups/:groupId, PUT /calendars/groups/:groupId/status to manage teams.
POST /calendars/groups, PUT /calendars/groups/:groupId, PUT /calendars/groups/:groupId/status
groupName, slug, status, members
Automate scheduling and certificate issuance without writing code.
Real-time synchronization between calendar events and Accredible certificates.
Custom automated workflows with calendar groups and triggers.
This glossary defines terms used in the Calendars API and Accredible Certificates integration with GHL, including API, endpoint, trigger, payload, and more.
Application Programming Interface: a set of rules that allows software components to communicate.
A specific URL in an API that performs a defined action.
An event that starts an automated workflow.
The data sent with an API request.
Trigger certificate issuance to automatically create and populate calendar events with reminders for learners.
Use free-slots data to propose appointment times when certificates become due.
Map groups in Calendars API to onboarding milestones for Accredible recipients.
In GHL, create API keys or OAuth credentials for the Calendars API and grant the required scopes.
Configure endpoint mappings and run tests against a sandbox environment.
Create triggers and actions to automate scheduling and certificate processes.
You’ll typically use OAuth 2.0 or an API key to authenticate with Calendars API and grant the calendars scope. Store credentials securely, rotate keys regularly, and test the integration in a sandbox before going live.
Yes. You can configure triggers to fire when specific calendar events occur or when workflow steps complete. Use mapping to control which Accredible actions run, such as issuing certificates or sending reminders.
Yes, endpoints require scopes like calendars.readonly or calendars.write depending on the action. Grant the minimum necessary permissions and monitor usage.
Testing: Use a sandbox environment and mock data. Validate triggers, payload formats, and error handling.
If a certificate is revoked, you can cancel or delete related calendar events. You can set up a webhook to update or remove events to reflect status.
Yes—by using groups and permissions, you can coordinate multi-user calendars. Configure team-based triggers so each group activity is isolated.
Rate limits depend on your GHL plan and API usage. Check the docs for quotas. If you hit limits, implement backoff strategies and batch requests.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
