Clio Calendar Entries API
Calendar Entries are used to track appointments or deadlines. Users can view Calendar Entries on any Calendar that they have “Viewer” or “Editor” permission for. Users can create Calendar Entries on any Calendar that they have “Editor” permission for.### Only supports dates on or after January 01 1900 00:00 UTC* If you attempt to create a date before 1900, the year of that date will be pulled forward to 1900 before it's persisted.### Calendar Update/Deletion Best Practices* Prior to updating or deleting a calendar entry, check for recurrence.* If the recurrence_rule parameter is not equal to `null`, offer the following 3 options for the update/deletion, as well as the note: 1. Only this instance: Update/Delete this event, but leave all future events unchanged. 2. All following: Updates/Deletes this event and all the future events. 3. All events in the series: Updates/Deletes all events in the series. * Note: If you've modified any future events in this series, those edits will be lost once youmake this change.[Support Link](https://help.clio.com/hc/en-us/articles/9289905071387-Calendar-Events)
Clio Calendar Entries API is one of 85 APIs that Clio publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Calendar Entries. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.
This API exposes 5 operations across 2 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version v4.
Requests are made against 4 base URLs: https://app.clio.com/api/v4, https://eu.app.clio.com/api/v4, https://ca.app.clio.com/api/v4, https://au.app.clio.com/api/v4.
Metadata
The identity and technical contract details declared by the specification.
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Calendar Entries are used to track appointments or deadlines. Users can view Calendar Entries on any Calendar that they have “Viewer” or “Editor” permission for. Users can create…
Schemas 15
The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are Activity_base (25 properties), Matter_base (23 properties), CalendarEntry_base (21 properties), Calendar_base (12 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Clio 12
Other APIs Clio publishes across the network.
This is an independent, third-party profile of Clio Calendar Entries API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.