Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kumospace Calendar API

The Calendar API from Kumospace — 7 operation(s) for calendar.

Kumospace Calendar API is one of 23 APIs that Kumospace publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Calendar. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 7 operations across 7 paths, and defines 9 schemas. It is described by OpenAPI 3.0.0.

Requests are made against a single base URL, /.

7 operations 7 paths 9 schemas 2 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
Base URL
https://api.kumospace.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Kumospace Calendar API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (firebase).

Paths & Operations 7

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

Calendar 7
POST
/v1/calendar/integrate-gcal
Enables Google Calendar integration for the user.
IntegrateGcal body → 200
GET
/v1/calendar/events/{queryDateYYYYMMDD}
Fetches the user's GCal events.
GetEventsForDate 2 params → 200
GET
/v1/calendar/events
GetEventsForRange 2 params → 200
POST
/v1/calendar/update-event-reply
Updates an event's reply status (accepted, declined, tentative).
UpdateAttendance body → 200
POST
/v1/calendar/update-connected-calendars
Updates a user's connected calendar preferences.
UpdateConnectedCalendars body → 200
POST
/v1/calendar/sync-calendars
Syncs a user's subscribed calendars in [Gcal/Outlook], with our integration doc.
SyncCalendars → 200
POST
/v1/calendar/disconnect-calendar-integration
Disconnect Calendar integration for the user. This will delete the corresponding integration doc in firestore.
DisconnectCalendarIntegration1 → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are ApiCalendarEvent (15 properties), ApiCalendarEventAttendee (5 properties), ApiCalendar (4 properties), ApiUpdateCalendarEventReplyRequest (2 properties). Each schema is shown below with its type and property counts.

ApiCalendarEvent
object
A Calendar Event.
15 properties 13 required
ApiUpdateCalendarEventReplyRequest
object
A request to update event reply status
2 properties 2 required
CalendarEventReplyStatus
string
These calendar response statuses match the Google Calendar API.
ApiCalendarEventAttendee
object
An object for attendee related information for the client.
5 properties 3 required
ApiEnableGcalIntegrationRequest
object
A request to enable Google Calendar integration.
1 property
ApiCalendar
object
ApiCalendar is a Calendar resource identifier, along with any state we need. We persist this object as is in firestore, because we want to track the isConnecte…
4 properties 4 required
CalendarEventStatus
string
These calendar statuses match the Google Calendar API.
ApiCalendarSource
string
Identifies the external source where this calendar was fetched from.
ApiUpdateConnectedCalendarsRequest
object
A request to update the user's connected calendars preferences.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kumospace-calendar-api-openapi.yml Raw ↑

Other APIs Kumospace publishes across the network.

Kumospace Account API
Kumospace Analytics API
Kumospace Chat API
Kumospace Daily (Webhook) API
Kumospace Demo API
Kumospace Flooring API
Kumospace Furniture API
Kumospace Integrations API
Kumospace MusicTrack API
Kumospace Payments API
Kumospace Recordings API
Kumospace Redirects API