Release Notes¶

Version 1.11¶

Released: September 3, 2026

This release adds a meeting search endpoint to the Partner User API with the same full-text behavior as in-product search, and tightens webhook auto-disable so a misconfigured endpoint is disabled promptly.

Version 1.10¶

Released: August 5, 2026

This release adds a Backlog Items API, corrects the advertised item_type values for agenda items, makes updating an agenda item's type actually work, lets you control where an agenda item sits in the agenda, adds presenter names and emails to agenda items, and withdraws the restricted_to_leads agenda-item flag.

{
  "presenters": ["123e4567-e89b-12d3-a456-426614174003"],
  "presenter_details": [
    {
      "user_id": "123e4567-e89b-12d3-a456-426614174003",
      "name": "John Doe",
      "email": "john.doe@example.com"
    }
  ]
}

Contract Changes¶

• New endpoints: seven /v1/partner/user/backlog-items operations (listBacklogItems, createBacklogItem, getBacklogItem, updateBacklogItem, deleteBacklogItem, assignBacklogItem, listBacklogItemHistory) and five /v1/partner/user/meetings/{id}/attachments operations (listMeetingAttachments, createMeetingAttachment, getMeetingAttachment, deleteMeetingAttachment, downloadMeetingAttachment). Additive — existing integrations are unaffected.
• Response: presenter_details added to the agenda item schema returned by GET, POST and PUT /v1/partner/user/meetings/{id}/agenda-items. presenters is retained and marked deprecated. name and email are populated only for presenters in the authenticated user's workspace; every presenter ID is reported either way.
• Response (behaviour change): PUT /v1/partner/user/meetings/{id}/agenda-items/{item_id} now returns the item's presenters in presenters instead of an empty array.
• POST /v1/partner/user/meetings/{id}/agenda-items and PUT /v1/partner/user/meetings/{id}/agenda-items/{item_id} — item_type now accepts DISCUSSION, QUESTIONS_TO_ANSWER, BREAK, ADJOURN; anything else returns 400 invalid_item_type.
• PUT /v1/partner/user/meetings/{id}/agenda-items/{item_id} — item_type sent in the body is now applied. It was previously accepted and silently ignored.
• POST /v1/partner/user/meetings/{id}/agenda-items and PUT /v1/partner/user/meetings/{id}/agenda-items/{item_id} — new optional sequence request field. An omitted sequence on create now appends the item after the meeting's last item instead of leaving it unordered.
• Response: restricted_to_leads has been removed from all agenda-item response schemas.
• Toolkit input (backward compatible): Existing toolkit manifests that still set restricted_to_leads on an agenda item remain schema-valid and accepted. The property is now marked deprecated in the toolkit manifest schema, is ignored, and has no effect. No manifest changes are required, but new manifests should omit it.
• OpenAPI, Postman collection, and agent-bundle artifacts regenerated.

Migration¶

• Replace DECISION, ACTION_ITEM and INFORMATION with DISCUSSION (or the type that matches your intent).
• If your integration read restricted_to_leads from agenda-item responses, remove that dependency — the field is gone and the underlying restriction no longer exists.
• No action is required for toolkit authoring; the input is silently ignored.

Version 1.9.1¶

Released: July 27, 2026

This patch extends the DNS/TXT domain ownership verification feature from 1.9.0 with outbound webhook events for Partner SSO IdP domain verification state changes, so your app can react to domain lifecycle transitions without polling.

Contract Changes¶

• New webhook events: partner.idp.domain_verified, partner.idp.domain_verification_failed, partner.idp.domain_revoked.
• AsyncAPI spec, webhook documentation, OpenAPI, Postman collection, and agent-bundle artifacts regenerated.

Action Item Webhook Delivery¶

• A user-originated completion of an assigned action item now delivers both the general action_item.updated event and the transition-specific action_item.completed event. Consumers subscribed to both should treat action_item.updated as the current-state notification and action_item.completed as the completion transition, rather than as two separate completions.
• A completion reconciled from an external TODO provider delivers action_item.updated only. Contio does not emit action_item.completed for that path because the provider response does not identify a Contio user for the required completed_by_user_id field.

Version 1.9.0¶

Released: July 20, 2026

This release adds DNS/TXT domain ownership verification for Partner SSO. Partners must now prove control of every email domain before claiming it in a strict-mode IdP configuration.

Name:  _contio-challenge.<domain>
Value: contio-domain-verify=<token>

Contract Changes¶

• POST /v1/partner/admin/idp/domains/{domain}/verify — Initiate (or rotate) a DNS/TXT domain ownership challenge.
• GET /v1/partner/admin/idp/domains/{domain} — Get the current verification status for a domain.
• POST /v1/partner/admin/idp/domains/{domain}/check — Perform the DNS TXT lookup and mark the domain verified on success.
• POST /v1/partner/admin/idp and PUT /v1/partner/admin/idp — Claiming an unverified domain in strict mode now returns 400 domain_not_verified.
• OpenAPI, Postman collection, and agent-bundle artifacts regenerated.

Version 1.8.1¶

Released: July 2, 2026

New Documentation¶

• Feature Gating Guide - Explains the Partner API 402 response and proper handling for plan-gated features by workspace.
• User Preferences Guide — Users may tailor their Contio experience via preferences which also affect the Partner API.

Contract Changes¶

• GET /v1/partner/user/meetings/{id}/transcript/export - Download a meeting transcript in SRT format (Elite plan)
• POST /v1/partner/user/meetings - Updated description in the OpenAPI specification to note that meeting access is resolved from the creating user's Sharing Defaults preference.
• OpenAPI, Postman collection, and agent-bundle artifacts regenerated.

Version 1.8.0¶

Released: June 11, 2026

This release introduces opt-in idempotency across most Partner API mutation endpoints, plus agent-native resources to enhance agentic Partner app development.

New Documentation¶

• Idempotency Guide — Explains the mechanism, headers, error codes, retention policy, exclusions (multipart), and best practices.
• Agent Integration Guide — How to point coding agents and LLM toolchains at the Partner API using llms.txt, operations.json, or the MCP manifest.

Contract Changes¶

• Idempotency-Key header documented on applicable mutation operations in the OpenAPI specification.
• Three new error codes: idempotency_key_reuse (422), idempotency_conflict (409), idempotency_key_invalid (400).
• OpenAPI, Postman collection, and agent-bundle artifacts regenerated.

Version 1.7.1¶

Released: May 22, 2026

Housekeeping: Update SDK to incorporate latest webhook specs; tidy sample toolkits to remove extraneous/unsupported attributes.

Version 1.7.0¶

Released: May 16, 2026

This release adds Toolkit Distribution for automated version propagation across workspaces, Workflow Dry-Run Mode for pre-execution simulation, and several enhancements to the Workflow and Agenda Item APIs.

New Admin Endpoints¶

Modified Admin Endpoints¶

PATCH /v1/partner/admin/toolkits/{id} — Two new optional fields:

POST /v1/partner/admin/toolkits/{id}/versions/{vid}/publish — New optional propagation field:

The publish response now includes a propagation object with mode, workspaces_queued, and workspaces_skipped_opted_out counts.

Additional Improvements¶

• Action button invocation tracking — POST /v1/partner/user/meetings/{id}/action-buttons/{button_id}/trigger now returns an invocation_id for correlating trigger events with downstream processing.
• Toolkit provenance — Template responses now include provenance metadata (toolkit origin, slug, and version) when the template was created via a toolkit manifest.
• Toolkit import conflict detection — Creating a toolkit version now validates the manifest against existing entities. Name/slug conflicts are returned as structured conflicts in the response, with a force: true option to override.

Version 1.6.0¶

Released: April 17, 2026

This release adds Workflow APIs and Workflow lifecycle webhooks so partners can discover workflow templates, trigger runs programmatically, and receive notifications as runs and tasks progress. It also streamlines the Partner Admin API surface by making Next Steps, Action Buttons, and Shortcuts toolkit-only entities. These "leaf" entities are now created, updated, and deleted exclusively through the Toolkit Manifest — their standalone Admin CRUD endpoints have been removed.

Templates remain available as standalone entities because they have independent value outside the toolkit lifecycle (e.g., browsing, assigning to meetings).

Version 1.5.0¶

Released: April 3, 2026

This major release introduces Toolkits — a declarative system for defining and deploying complete meeting experiences. Partners can now bundle templates, AI-powered next steps, and action buttons into versioned manifests that install atomically across workspaces.

Toolkit Manifest System¶

Define complete meeting experiences in a single JSON document:

{
  "templates": [
    {
      "$id": "sales-call",
      "name": "Sales Discovery Call",
      "next_steps": [
        { "next_step": { "$ref": "meeting-summary" }, "order": 1 }
      ]
    }
  ],
  "next_steps": [
    {
      "$id": "meeting-summary",
      "name": "Generate Summary",
      "type": "ai",
      "prompt": "Summarize this sales call including key discussion points.",
      "action_buttons": [
        { "action_button": { "$ref": "email-btn" }, "order": 1 }
      ]
    }
  ],
  "action_buttons": [
    {
      "$id": "email-btn",
      "name": "Send via Email",
      "delivery_type": "email"
    }
  ]
}

Key Features

• Atomic Installation — All entities install together or not at all
• Reference System — Use $id and $ref to link entities within the manifest
• Version Control — Store manifests in your repository and deploy programmatically
• Multi-Workspace — Install the same toolkit across multiple workspaces

See the Toolkit Manifests Guide for complete documentation and examples.

Admin API Endpoints¶

Toolkit Management

Toolkit Versioning

Template Management

User API Endpoints¶

Toolkits

Templates

Meeting Next Steps & Action Buttons

SDK Examples¶

Create and Install a Toolkit

import { ContioPartnerSDK } from '@contio/partner-sdk';

const sdk = ContioPartnerSDK.forAdmin({ apiKey: process.env.API_KEY });

// Create toolkit from manifest
const toolkit = await sdk.admin.createToolkit({
  name: 'Sales Workflow',
  description: 'Post-meeting follow-up automation',
  manifest: salesManifest
});

// Install on a workspace
await sdk.admin.installToolkit(toolkit.id, {
  workspace_id: 'ws_abc123'
});

Execute Meeting Next Steps

const userSdk = ContioPartnerSDK.forUser({
  clientId: process.env.CLIENT_ID,
  clientSecret: process.env.CLIENT_SECRET,
  redirectUri: 'https://your-app.com/callback'
});

// Get next steps for a meeting
const nextSteps = await userSdk.user.getMeetingNextSteps(meetingId);

// Execute AI-powered next step
const execution = await userSdk.user.executeNextStep(meetingId, nextStepId);

// Poll for result
const result = await userSdk.user.getNextStepResult(meetingId, nextStepId);
console.log(result.output); // AI-generated content

OAuth Scopes¶

New scopes for Toolkit access:

New Webhook Events¶

Three new webhook events support the Toolkit system:

Example: next_step.completed Payload

{
  "event_type": "next_step.completed",
  "event_id": "evt-550e8400-e29b-41d4-a716-446655440000",
  "timestamp": "2026-04-01T10:30:00Z",
  "partner_app_id": "app-550e8400-e29b-41d4-a716-446655440000",
  "for_user": {
    "id": "user-550e8400-e29b-41d4-a716-446655440000",
    "email": "user@example.com"
  },
  "data": {
    "next_step_id": "ns-550e8400-e29b-41d4-a716-446655440000",
    "next_step_name": "Generate Meeting Summary",
    "meeting_id": "mtg-550e8400-e29b-41d4-a716-446655440001",
    "result_id": "nsr-550e8400-e29b-41d4-a716-446655440003",
    "executed_by": "user-550e8400-e29b-41d4-a716-446655440004",
    "executed_at": "2026-04-01T10:30:00Z",
    "execution_mode": "manual"
  }
}

See the Webhook Events Reference for complete payload schemas.

Version 1.4.7¶

Released: March 20, 2026

This release introduces the Chat Session API, enabling partners to programmatically interact with the Contio AI agent through asynchronous, turn-based conversations. Sessions can optionally be scoped to meetings and primed with context documents for targeted AI assistance.

Chat Session Endpoints¶

Key Features¶

• Turn-based conversations — Each session tracks user and agent messages as ordered turns with 0-based sequence numbering
• Meeting-scoped sessions — Optionally associate a session with a meeting so the AI agent has full meeting context
• Context document priming — Attach context documents (uploaded via the Meeting Context API) to give the agent additional reference material
• Partner metadata — Attach up to 10 key-value pairs to sessions for your own tracking purposes
• Idempotent creation — Use the Idempotency-Key header to safely retry session creation without duplicates
• Turn pagination — Retrieve session turns with configurable turn_limit and turn_offset parameters
• Agent metadata — Agent turns include tool call details, referenced documents, and token usage statistics

OAuth Scopes¶

• New chat:read scope grants read access to sessions and turns (list, get)
• New chat:write scope grants write access (create sessions, send messages) and implicitly includes chat:read capability

Limits¶

Version 1.4.6¶

Released: March 13, 2026

This release introduces the Meeting Context API, enabling partners to upload, retrieve, and manage supplemental context documents for meetings. Context documents are preprocessed for use during AI-powered meeting summarization and action item extraction.

Meeting Context Endpoints¶

• POST /v1/partner/user/meetings/{id}/context — Upload a context document for a meeting
• GET /v1/partner/user/meetings/{id}/context — List all context documents for a meeting
• GET /v1/partner/user/meetings/{id}/context/{context_id} — Get a specific context document
• GET /v1/partner/user/meetings/{id}/context/{context_id}/content — Download context document content
• DELETE /v1/partner/user/meetings/{id}/context/{context_id} — Delete a context document

OAuth Scopes¶

• New context:read and context:write scopes control access to Meeting Context endpoints
• These scopes are independent of the existing meetings:read and meetings:write scopes

Version 1.4.5¶

Released: March 06, 2026

This release adds webhook management capabilities: automatic webhook disabling on repeated delivery failures, manual webhook status control, and event filtering with include/exclude modes.

Webhook Auto-Disable¶

• Webhooks are automatically disabled after 50 consecutive abandoned deliveries or 72 hours without a successful delivery
• Partners are notified via email when auto-disable triggers
• New deliveries are recorded as pending while disabled, preserving events for later delivery
• Feature-flagged via webhook_auto_disable

Webhook Status Management¶

• PUT /v1/partner/admin/webhook-status — Enable or disable webhooks manually
• pending_disposition option: choose deliver (retry pending events) or abandon (discard pending events) when re-enabling
• SDK: admin.updateWebhookStatus({ enabled: true/false })

Webhook Event Filtering¶

• PUT /v1/partner/admin/webhook-filter — Set include or exclude filter for event types
• DELETE /v1/partner/admin/webhook-filter — Remove filter (receive all events)
• 15 filterable event types; user.connection.revoked always bypasses filters
• SDK: admin.setWebhookFilter({ ... }) and admin.removeWebhookFilter()

Version 1.4.3¶

Released: February 27, 2026

This backward-compatible release adds shared workspace support to the Partner OAuth connect flow, allowing partners to provision multiple users into the same workspace.

Shared Workspace Provisioning¶

• The POST /auth/initiate endpoint now accepts optional workspace_id and is_admin fields. When workspace_id is provided, the new user is added to the specified existing workspace instead of creating a personal workspace.
• is_admin: true assigns the WORKSPACE_ADMIN role; is_admin: false (default) assigns WORKSPACE_MEMBER.
• New validation error codes: workspace_not_found (404), workspace_not_authorized (403), workspace_conflict (409).
• The 409 conflict response includes the user's current workspace_id as a dedicated field for programmatic reconciliation.

Profile Enhancement¶

• The GET /v1/partner/user/profile endpoint now returns workspace_id, workspace_name, and workspace_role fields.

Version 1.4.2¶

Released: February 17, 2026

This backward-compatible release standardizes the date search query parameters and error responses across all Partner API endpoints.

• The "start_date" and "end_date" query parameters are now fully supported for meetings and action items search endpoints.
• The calendar search endpoint now also expects "start_date" and "end_date" query parameters for consistency. The "start" and "end" query parameters have been deprecated and will be removed in a future version.
• Error responses have been standardized for all endpoints. The "error" and "request_id" fields are now utilized consistently, and the "message" field has been deprecated.
• API documentation has been updated to reflect these improvements and deprecations.

Version 1.4.0¶

Released: January 31, 2026

This release adds calendar event details retrieval and comprehensive webhook events for meeting updates, calendar sync, and agenda item lifecycle tracking.

Calendar Event Details¶

Retrieve full details of a specific calendar event by ID.

New Endpoint

Key Features

• Retrieve complete calendar event information including title, times, and attendees
• Access organizer details and attendee list with response status
• Supports both timed and all-day events

Example Usage

// Get calendar event details
const event = await sdk.user.getCalendarEvent(calendarEventId);

console.log(event.title);           // "Product Planning Meeting"
console.log(event.start_time);      // "2026-01-31T10:00:00Z"
console.log(event.attendee_count);  // 5

New Webhook Events¶

Seven new webhook events provide real-time notifications for meeting updates, calendar sync, and agenda item lifecycle.

Meeting Events

Calendar Events

Agenda Item Events

See the Webhook Events Guide for complete event schemas and examples.

Version 1.3.0¶

Released: January 21, 2026

This release significantly expands the Partner User API with comprehensive meeting collaboration capabilities. Partners can now manage meeting participants, agenda items, and calendar integrations, enabling deeper integration with MeetingOS workflows.

Meeting Participant Management¶

Programmatically manage meeting participants through the Partner User API.

New Endpoints

Key Features

• Add participants by email (supports both registered users and guests)
• Assign participant roles: EDITOR or VIEWER
• Automatic guest provisioning when adding new participants
• View all participants with roles and metadata

Example Usage

// List participants
const participants = await sdk.user.getMeetingParticipants(meetingId);

// Add a participant
await sdk.user.addMeetingParticipant(meetingId, {
  email: 'john.doe@example.com',
  name: 'John Doe',
  role: 'EDITOR'
});

// Remove a participant
await sdk.user.removeMeetingParticipant(meetingId, participantId);

Agenda Item Management¶

Create, update, and delete agenda items within meetings.

New Endpoints

Key Features

• Create structured agenda items with titles, descriptions, and time allocations
• Support for multiple item types: DISCUSSION, DECISION, UPDATE, etc.
• Automatic synchronization with Tiptap collaborative editor
• Update or delete agenda items as needed

Example Usage

// Create an agenda item
const newItem = await sdk.user.createAgendaItem(meetingId, {
  item_type: 'DISCUSSION',
  title: 'Q4 Budget Review',
  description: 'Review and approve Q4 budget allocation',
  time_allocation_minutes: 15
});

// Update an agenda item
await sdk.user.updateAgendaItem(meetingId, itemId, {
  title: 'Updated Title',
  time_allocation_minutes: 20
});

Calendar Integration¶

Access user calendar events and link them to meetings.

New Endpoints

Key Features

• Query calendar events with date range filtering
• Link existing calendar events to MeetingOS meetings
• Create meetings automatically from calendar events
• Access calendar event metadata (attendees, location, times)

Example Usage

// Get calendar events
const events = await sdk.user.getCalendarEvents({
  start: '2026-01-01T00:00:00Z',
  end: '2026-01-31T23:59:59Z',
  limit: 50
});

// Create meeting from calendar event
const result = await sdk.user.createMeetingFromCalendarEvent({
  calendar_event_id: calendarEventId
});

Enhanced Webhook Events¶

Six new webhook events provide real-time notifications for meeting and action item lifecycle.

New Events

See the Webhook Events Guide for complete event schemas and examples.

Version 1.2.1¶

Released: January 17, 2026

Minor improvements to OAuth and webhook handling.

Changes

• Added login_hint parameter support in getAuthorizationUrl()
• Added support for id_token introspection and verification
• New Express middleware for webhook signature verification

Version 1.2.0¶

Released: January 8, 2026

This release introduces a new opaque token format for improved security and privacy.

Opaque Token Format¶

Access and refresh tokens now use a consistent, versioned format that abstracts internal implementation details.

What's New

• New Token Format - Access tokens: cto_at_v1_..., Refresh tokens: cto_rt_v1_...
• Improved Security - Tokens no longer expose internal claims or metadata
• Version Routing - Token version prefix enables seamless future upgrades

Version 1.1.0¶

Released: January 2, 2026

This release introduces Partner IdP SSO, enabling your users to sign in to Contio using your corporate identity provider.

Single Sign-On (SSO) Integration¶

New Features

• SSO Integration Guide - Step-by-step guide for configuring your OIDC-compliant identity provider
• User Provisioning Guide - Documentation explaining automatic user provisioning during OAuth
• SDK SSO Methods - New getIdpLoginUrl() and getSsoStatusUrl() methods

How It Works

1. Users connect to Contio via OAuth (establishing consent and provisioning)
2. Configure your identity provider in the Partner Dashboard
3. Users can then sign in using your corporate credentials via SSO

Version 1.0.1¶

Released: December 16, 2025

Documentation improvements and new documentation site launch.

Changes

• Launched official documentation site at docs.contio.ai/partner-api
• Slimmed down SDK README to essentials with links to full documentation
• Removed bundled docs/ folder from SDK distribution (now served from docs site)
• Added comprehensive guides: OAuth Flow, Credential Management, Troubleshooting
• Added detailed API reference with code examples

Version 1.0.0¶

Released: November 15, 2025

Initial release of the Contio Partner SDK.

Features

• OAuth 2.0 authentication with PKCE support
• Meeting data access (summaries, notes, transcripts)
• Action item management
• Webhook event handling with signature verification
• TypeScript support with full type definitions