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 Integrations API

The Integrations API from Kumospace — 8 operation(s) for integrations.

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

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

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

Requests are made against a single base URL, /.

8 operations 8 paths 5 schemas 1 DELETE2 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 Integrations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (firebase).

Paths & Operations 8

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

Integrations 8
GET
/v1/users/me/integrations
List connected integrations
GetSelfIntegrations → 200
DELETE
/v1/integrations/{integrationId}
Disconnect a user integration. This also deletes the integration doc.
DisconnectOwnIntegration 1 param → 204
POST
/v1/integrations/microsoft-outlook/handle-redirect
Handles the redirect from the microsoft graph authorize URL. This is a redirect endpoint, shouldn't be called by us
HandleConnectOutlookIntegration → 204
POST
/v1/integrations/microsoft-teams-status/handle-redirect
Handles the redirect from the microsoft graph authorize URL. This is a redirect endpoint, shouldn't be called by us
HandleConnectTeamsInCallStatus → 204
POST
/v1/integrations/microsoft-teams-status/webhook/presence-subscription/{id}
Handles the subscription to the microsoft presence API. This is a webhook endpoint, shouldn't be called by us
Handle 1 param body → 204
GET
/v1/integrations/zoom-status/handle-redirect
Handles the redirect from the zoom oauth. This is a redirect endpoint, shouldn't be called by us
HandleConnectZoomInCallStatus 2 params → 204
POST
/v1/integrations/zoom-status/webhook/participant-update
Handles the zoom participant updates. This is a webhook endpoint, shouldn't be called by us
HandleParticipantUpdate body → 200204
POST
/v1/integrations/zoom-status/deauthorize
DeauthorizeZoomIntegration body → 204

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are APIUserIntegration (4 properties), ZoomParticipantUpdateEvent (3 properties), ZoomValidationEvent (3 properties), ZoomDeauthorizedEvent (2 properties). Each schema is shown below with its type and property counts.

ZoomValidationEvent
object
3 properties 3 required
ZoomDeauthorizedEvent
object
2 properties 2 required
ZoomParticipantUpdateEvent
object
3 properties 3 required
Integration
string
APIUserIntegration
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kumospace-integrations-api-openapi.yml Raw ↑

Other APIs Kumospace publishes across the network.

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