Set up securely by generating API keys or OAuth tokens and granting calendars.write scope to enable create read update and delete operations.
Authorize 17hats to access your Calendars data using approved OAuth flow ensuring permissions align with required scopes.
Key endpoints used with 17hats 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, 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 a new event is created in 17hats, automatically create a matching calendar in Calendars API.
Actions: Use POST /calendars/ to create a calendar, then link events to that calendar.
POST /calendars/
calendarName, timeZone, color, location
Trigger: When a user requests calendar data in 17hats, fetch calendars via GET /calendars/.
Actions: Retrieve with GET /calendars/ and GET /calendars/:calendarId to pull details.
GET /calendars/
calendarId, name, status, owner
Trigger: Look up available slots for a selected calendar when scheduling in 17hats
Actions: Use GET /calendars/:calendarId/free-slots to fetch open times
GET /calendars/:calendarId/free-slots
calendarId, date, timeSlot
Automate scheduling tasks without writing code
Keep your calendars in sync across platforms in real time
Create powerful workflows using triggers and actions to streamline appointments
A quick glossary of terms like API endpoint authentication resource trigger and action used throughout this integration guide
A specific URL and HTTP method used to perform an action with the Calendars API
The process of verifying identity and obtaining permission to access the Calendars API
A data object representing a calendar that can hold events and availability
Time windows when a calendar has no events and is available for scheduling
Automatically sync new 17hats events to a dedicated calendar in Calendars API to avoid duplicate data
Offer time slots based on real time free slots from the API to optimize booking
Manage multiple calendars for a team with group endpoints and access controls
Obtain OAuth tokens with the calendars.write scope and securely store credentials
Map fields like calendarName to app data and test each endpoint
Run tests, set up error handling, and deploy to production with monitoring
Calendars API is a RESTful interface that lets you manage calendars, events and availability from within your workflow. It supports creating reading updating and deleting calendars and related resources. This FAQ explains how Calendars API connects with 17hats, what endpoints exist, and the best practices for setup.
Authentication uses OAuth or API keys depending on your setup. You will obtain access tokens with the calendars.write scope to perform create update and delete operations. Keep tokens secure, refresh before expiry, rotate secrets regularly, and follow least privilege principles.
Common endpoints include POST /calendars, GET /calendars, PUT /calendars/:calendarId and GET /calendars/:calendarId/free-slots. Group related endpoints enable managing calendars groups and resources; test endpoints in a sandbox environment before production.
No code integration is possible with modern automation platforms that support REST logic. You can also call the API directly if you need custom behavior. If you require advanced customization beyond connectors, light scripting can help.
To get free slots, call GET /calendars/:calendarId/free-slots for the chosen calendar. The response returns available time windows you can present to users for scheduling.
Yes you can test in a sandbox or with test calendars. Use mock data and review responses before enabling production integrations.
Rate limits vary by plan and endpoint. Plan accordingly and implement exponential backoff. If you exceed limits, retry later or contact support for higher quotas.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
