REST API

Strata is built on a REST API described by an OpenAPI 3.1 specification. Most integrations use the MCP server or the generated SDK rather than calling REST directly, but the full spec is available for tooling and custom clients.

SPEC

OpenAPI specification

The machine-readable spec is served live and stays in sync with the deployed API. Open it directly, or import it into a viewer like Scalar, Redoc, Postman, or Insomnia:

Open openapi.json

The spec is also advertised for agents and crawlers via /.well-known/api-catalog.

CONVENTIONS

Base URL and versioning

Every endpoint lives under /api/v1 on the API host; the path prefix carries the version.

AUTH

Authentication

Requests carry a bearer token. Browser sessions use a short-lived access token minted from an HttpOnly refresh cookie; programmatic MCP access uses OAuth 2.1. The generated SDK handles token injection and refresh for you.

REFERENCE

Resource areas

The API spans the full Strata domain. The main resource areas:

Documents: CRUD, history, comments, suggestions, access, publishing, images
Spaces: membership, sources, access grants, hybrid search
Companies, organizations, and tiers: the workspace hierarchy
Users and profiles: accounts, memberships, public profiles
Access and sharing: permissions, public links, space grants
Auth and OAuth: sessions, tenant switching, MCP OAuth clients
Agents and tasks: platform and user agent invocation
Admin and compliance: SSO, SCIM, audit, retention, billing

SDK

Generated SDK

The TypeScript SDK (@strata/shared) and a Rust client are generated from the same spec, so types stay in lockstep with the API.

Prefer tools over raw REST? See the MCP Tools Reference.