Skip to main content
The Sapt REST API gives you direct HTTP access to Projects, agents, memory, actions, and everything else in the workspace for that Project. Prefer to connect Claude or ChatGPT? See the MCP Connector.

Base URL

Authentication

All requests require an API key in the Authorization header:
Create API keys under Account > API Keys in the Sapt dashboard. See Authentication for the steps and the other ways to sign in.

Content type

Request and response bodies use JSON, except media uploads, which take raw bytes:

Error responses

Errors return a structured envelope. code is machine-readable, message is human-readable, and details is present for field-level validation errors or additional context.
See Errors for every code.

Endpoint reference

Every public endpoint is auto-generated from the live OpenAPI spec. Browse them under Reference.

Reading the reference

A few fields are free-form JSON: their exact shape depends on the resource, so the reference shows them as an open object rather than a fixed schema. The most common ones: If a field shows up as an open or “unknown” object, treat it as JSON whose keys depend on the specific resource, not as a typo or a missing type.

Status codes

Example request