Docs

Command Palette

Search for a command to run...

Docs/API

API

Current Wyatt API availability, public ingest, and how agents authenticate.

Overview

Wyatt exposes workspace APIs over HTTP using JSON and public IDs. Supported /api/v1 routes authenticate with an Ory session (browser cookie or native session token) or an Ory-issued OAuth access token. Workspace API keys from Settings are not accepted as Authorization: Bearer credentials on those routes.

Current API status

Legacy public resource APIs are retired. Supported Wyatt APIs use public IDs.

Public resource routes are no longer available. The old /api/public/v1 folder, PDF, database, document, and whiteboard routes now return 410 Gone instead of advertising unsupported numeric-ID behavior.

Public markdown ingest is served by the regional Wyatt data plane at POST /api/v1/public/ingest/markdown/{token}. Copy the current ingest URL from a folder's Ingest Links dialog.

Authentication

The standard /api/v1 route group uses AuthMiddlewareWithOAuth. A bearer value is classified by shape:

  • Ory-issued OAuth access tokens are verified against Ory's key set.
  • Other bearer values and browser cookies are validated as Ory sessions through Kratos.

A workspace API key in an Authorization: Bearer header is rejected with 401 Invalid session. Do not paste a Settings API key into curl, MCP config, or an agent prompt.

Agents should connect through MCP with OAuth. Follow the MCP Quickstart. OAuth connections to Google, Slack, GitHub, and other providers are configured in Connections.

Next Steps