Authorize via OAuth 2.0 or API keys and store tokens securely. Reuse access tokens when connecting to ActiveCollab.
Grant ActiveCollab the required scopes for calendars management, including calendars.write and calendars.readonly.
POST /calendars/ — Create a new calendar PUT /calendars/:calendarId — Update a calendar DELETE /calendars/:calendarId — Delete a calendar calendars.readonly — Read only access for calendars GET /calendars/ — List calendars GET /calendars/:calendarId — Get a single calendar GET /calendars/:calendarId/free-slots — Retrieve available time slots calendars.groups.readonly — Read only access for calendar groups GET /calendars/groups — List calendar groups calendars/groups.write — Write access for groups POST /calendars/groups — Create a calendar group POST /calendars/groups/validate-slug — Validate a group slug DELETE /calendars/groups/:groupId — Delete a calendar group PUT /calendars/groups/:groupId — Update a calendar group PUT /calendars/groups/:groupId/status — Change group status calendars/resources.readonly — Read only access for resources GET /calendars/resources/:resourceType — List resources by type
Trigger: When a new project is created in ActiveCollab, automatically create a calendar in Calendars API.
Actions: map project dates to calendar events, assign owners, set reminders.
POST /calendars/
Key fields: name, timeZone, color, ownerId
Trigger: when a group is created or updated in ActiveCollab
Actions: propagate group membership, update shared calendar entries
PUT /calendars/groups/:groupId
Key fields: groupId, calendarId, syncStatus
Trigger: availability changes in ActiveCollab push to Calendars API
Actions: publish free slots, push reminders, update event status
GET /calendars/:calendarId/free-slots
Key fields: calendarId, resourceType, timeZone
No code automation to create calendars and events without custom code.
Real-time sync reduces manual data entry and errors.
Centralized calendar management across platforms for teams.
Definitions of key concepts to help you implement this integration and understand how calendars are managed.
A defined set of endpoints and methods that let apps talk to Calendars API.
A specific path and method combination on Calendars API used to perform an operation.
Process of proving identity and being granted access to the Calendars API.
A callback URL that receives event notifications from Calendars API.
Automatically generate a calendar in Calendars API when a new project is created in ActiveCollab and populate it with milestones.
Link ActiveCollab groups to shared calendars so team availability is visible in both tools.
Publish free slots from ActiveCollab into Calendars API events to accelerate meeting scheduling.
Register the app with the OAuth provider, note the client ID and client secret, and configure redirect URIs.
Use the OAuth flow or API key exchange in the ActiveCollab connector to obtain an access token.
Map calendars, groups and availability fields, then run tests and monitor logs.
The Calendars API exposes endpoints to create, read, update and delete calendars, groups and resources. It also provides access controls and slot availability data. Use these endpoints to build calendar workflows that fit your ActiveCollab setup. The API is designed to be easy to learn and implement even for first time integrators.
Authentication can be done via OAuth 2.0 or API keys. Create a connection from the App Connector in ActiveCollab, request the necessary scopes, and securely store tokens. Regularly refresh tokens as needed and rotate credentials to keep data secure.
Available endpoints cover calendars, calendar groups, and resources. You can create calendars, fetch lists, check free slots, manage groups, validate slugs, and retrieve resources by type. Use documentation to map the right endpoints to your ActiveCollab workflows.
Yes, you can manage groups using endpoints for listing, creating, updating and deleting groups as well as changing group status. This lets you organize calendars around teams or projects within ActiveCollab.
Webhooks are supported to notify your system of calendar events. Configure subscriptions for creates, updates or deletes to stay in sync without polling.
Yes. The integration supports no code flows via the Zapier App Connector and similar tools. You can set up basic calendar actions without writing code, then scale with API access when needed.
Test in a sandbox or staging environment. Use sample data to verify endpoints, monitor request logs, and validate field mappings before going live.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers