How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Chorus.ai Integrations Calendar API

The Integrations Calendar API from Chorus.ai — 4 operation(s) for integrations calendar.

Chorus.ai Integrations Calendar API is one of 22 APIs that Chorus.ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Integrations Calendar. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 4 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 26.33.08.

Requests are made against 2 base URLs: /, https://chorus.ai.

4 operations 4 paths 2 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
26.33.08
Base URL
https://chorus.ai/api/v1
Authentication
HTTP Basic, HTTP Bearer, API Key
Terms of Service
Resource Areas
1

Authentication & Security 3

Chorus.ai Integrations Calendar API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (basic). It accepts HTTP bearer tokens (bearer-token). An API key is passed in the header as x-ziaccesstoken (x-ziaccesstoken). By default, every request must be authenticated.

  • basic — HTTP basic authentication (for those APIs that support it).
  • bearer-token — A Chorus token or a signed JWT.
  • x-ziaccesstoken — A ZoomInfo access token.

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Integrations Calendar 4
GET
/api/v1/integrations/google_calendar/actions/connect
Connect Google Calendar service account
get-api-v1-integrations-google_calendar-actions-connect → 200400
POST
/api/v1/integrations/google_calendar/actions/verify
Verify calendar service account
post-api-v1-integrations-google_calendar-actions-verify body → 204400409
GET
/api/v1/integrations/office365_calendar/actions/connect
Connect Office365 Calendar service account
get-api-v1-integrations-office365_calendar-actions-connect → 302400
POST
/api/v1/integrations/office365_calendar/actions/verify
Verify calendar service account
post-api-v1-integrations-office365_calendar-actions-verify body → 204400409

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Error (1 property), VerifyCalendarServiceAccount (1 property). Each schema is shown below with its type and property counts.

VerifyCalendarServiceAccount
object
1 property 1 required
Error
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

chorus-ai-integrations-calendar-api-openapi.yml Raw ↑

Other APIs Chorus.ai publishes across the network.

Chorus.ai Auth API
Chorus.ai Conversations API
Chorus.ai Emails API
Chorus.ai Engagement filter API
Chorus.ai Event API
Chorus.ai External Moments API
Chorus.ai Integrations CRM API
Chorus.ai Integrations Email API
Chorus.ai Integrations Meet API
Chorus.ai Playlists API
Chorus.ai Public External Moments API
Chorus.ai Public Playlist Moments API
Where this information came from

This is an independent, third-party profile of Chorus.ai Integrations Calendar 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.