> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kynasmith.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# API reference

> Overview of the public HTTP API and related runtime guidance.

# API reference

The Kynasmith API is a RESTful HTTP API. All endpoints require bearer token authentication.

## Authentication

All API requests require an `Authorization: Bearer <access_token>` header. Mint access tokens using `POST /api/auth/access-tokens`. See [Authentication](/get-started/authentication) for details.

## Endpoints

The endpoint reference covers all public endpoints:

* Access-token exchange
* MoveSpec lifecycle (create, update draft, validate, version, release)
* Detection session creation and status
* Usage and health endpoints

## Guides

* [Runtime contract](/api-reference/runtime-contract) — Pose frame schema and event types
* [Realtime protocol](/api-reference/realtime-protocol) — Session lifecycle for direct API integrations
* [Error codes](/api-reference/error-codes) — Error code reference
* [Rate limits](/api-reference/rate-limits) — Request limits and retry strategies
* [API versioning](/api-reference/versioning) — Stability guarantees and deprecation policy

## Resource IDs

All resource IDs (`movespec_id`, `session_id`, `project_id`, etc.) are **opaque strings**. Always store and transmit them as strings. Do not parse, construct, or assume ordering within IDs.

## Request and response format

* Request bodies use JSON (`Content-Type: application/json`).
* Response bodies use JSON.
* Dates use ISO 8601 format (`2026-04-04T12:00:00Z`).
* All error responses follow the [standard error envelope](/api-reference/error-codes).

Use the [SDKs](/sdks/overview) for the recommended integration path, or the endpoint reference below for direct HTTP integration.