Snoze for developers

The workspace, programmable.

The same typed kernel that runs the app, exposed as a REST API, an MCP server and signed webhooks. Keys carry your permissions and nothing more.

QuickstartAPI reference

334 endpoints · OpenAPI 3.1 · llms.txt

curl
curl "https://api.snoze.dev/v1/items?kind=database" \
  -H "Authorization: Bearer $SNOZE_API_KEY"
{ "data": { "items": [
    { "id": "9f2c…3c85", "kind": "database",
      "title": "Production board" }
  ], "cursor": null } }

01 /Three ways in

REST API

Items, database records and files over JSON. The key pins the workspace, so paths are flat.

GET /v1/databases/{id}/records

MCP server

Hand a workspace to Claude, Cursor or any MCP client. Same permissions, same approval rules as the assistant.

https://api.snoze.dev/mcp

Webhooks

Signed, replayable deliveries for workspace events instead of polling.

POST https://your-app.dev/hooks

02 /First request to first webhook

01Create a keyWorkspace settings → API keys. Scope it to what the integration needs.02List your databasesGET /v1/items?kind=database with the key as a bearer token.03Read and write recordsQuery with a view or a search, create with title and data, patch what changed.04Go realtimeSubscribe to webhooks, or give the whole workspace to an agent over MCP.

03 /Reference

04 /Docs for machines

Every page is available as Markdown for agents. Point a model at the index or a single page.

GET /llms.txt
GET /llms-full.txt
GET /llms.mdx/docs/api/records