MeetKanoeGet started

Public API documentation

Structured MeetKanoe product facts for agents and integrations.

The MeetKanoe Public Product API is a small, versioned, read-only REST interface. It exposes the same non-sensitive product, feature, and plan information that appears on the public website. It does not expose accounts, assistants, meetings, recordings, transcripts, or any other private workspace data. The v1 endpoints require no API key or login.

Base URL and OpenAPI description

The stable base URL is https://www.meetkanoe.com/api/v1. Retrieve the complete OpenAPI 3.1 contract from /openapi.json. Every operation has a unique operation identifier, a description, and typed success and error schemas so an agent can translate it into a function call without guessing parameters or response fields.

Available endpoints

  • GET /api/v1 returns the API index, version, endpoint links, and authentication policy.
  • GET /api/v1/product returns the product identity, description, audience, supported meeting platform, and canonical public resources.
  • GET /api/v1/features returns the documented beta capabilities and their availability.
  • GET /api/v1/plans returns current advertised Personal, Kanoe Cloud, and Teams availability.

Authentication, writes, and private data

No authentication is required because these endpoints contain only public product facts. The API does not accept writes and does not create accounts, start recordings, modify meetings, or expose private content. Unsupported methods receive HTTP 405 with a JSON error object. Unknown public API paths receive HTTP 404 with an error code, message, resolution hint, and documentation link.

Versioning and compatibility

Stable operations use a major version in the URL, beginning with /api/v1. MeetKanoe may add backward-compatible response fields within v1. A breaking request or response change requires a new major path. If a stable version is scheduled for retirement, the developer documentation will describe the replacement and the API will advertise deprecation and sunset information at least 90 days before removal.

Rate limits and retry behavior

The public API uses a fixed window of 120 requests per client per 60 seconds. Every successful response includes RateLimit-Limit, RateLimit-Policy, RateLimit-Remaining, and RateLimit-Reset headers. A client that exceeds the limit receives HTTP 429 with the same rate-limit fields, a Retry-After header, and the standard structured JSON error object. Agents should wait for the declared interval instead of retrying in a tight loop.

Example request

curl -H "Accept: application/json" \
  https://www.meetkanoe.com/api/v1/product

Responses use JSON, allow cross-origin reads, and are marked private and no-store so per-client limit information is never shared through a cache. For the human-readable product workflow, use the main MeetKanoe documentation.