Skip to content

Contio MeetingOS User API

Welcome to the documentation for the Contio MeetingOS User API — the first-party /v1 API that lets you build on top of your own Contio workspace and its meetings, action items, calendars, and members.

What is the User API?

The User API is the first-party REST API for Contio MeetingOS. It authenticates your own account (or a personal access token you issue for yourself) against your own workspace — no partner agreement required.

Use the User API to:

  • Work with meetings: list, create, fetch, and delete meetings and their context
  • Manage action items: create, list, update, and delete action items
  • Structure agendas: create, list, update, and delete agenda items
  • Read calendars: list synced calendar events and fetch event details
  • Administer your workspace: manage members, API keys, and webhooks
  • Subscribe to events: register workspace webhooks for real-time notifications

Choosing a credential

The User API accepts two kinds of bearer credential in the Authorization: Bearer <token> header:

Best for native/desktop apps and CLIs acting on behalf of the signed-in user. Uses the authorization-code flow with PKCE (S256) and a loopback redirect (http://127.0.0.1:PORT). Access tokens are prefixed cto_at_v1_.

See the Authentication guide.

Best for scripts, cron jobs, and server-side automation. You issue a long-lived token scoped to a subset of your own grants; it is shown in plaintext exactly once. PATs are prefixed cto_pat_v1_.

See the Personal Access Tokens guide.

Resource Description
Getting Started Make your first authenticated request in minutes
Authentication OAuth 2.1 + PKCE loopback flow, refresh, and revocation
Personal Access Tokens Issue, list, and delete PATs
API Reference Endpoint catalog, scopes, and the interactive OpenAPI reference
Release Notes /v1 GA changelog

Base URL & versioning

All endpoints are served under the /v1 path prefix on the Contio API host:

https://api.contio.ai/v1

The API is versioned in the URL path. The OpenAPI reference is generated directly from the /v1 controllers and is the source of truth for request and response shapes — see the OpenAPI Specification.

Support