Context is Everything logo

APIs

Superseded: the supported third-party integration surface is now the MCP
server (/mcp) — see docs/prd/18-mcp-server.md. The REST API below remains
for internal (in-container) use only; no new external API keys should be issued.

Sasha started as a chat interface for your institutional knowledge. Now it goes where your work happens.

The Sasha API lets your applications tap into Sasha's capabilities programmatically — run AI-powered tasks on demand or on a schedule, join live meeting transcriptions, receive real-time events, and build workflows that would be impossible through a chat window alone.

Available APIs

General

API Description
Projects API List projects, browse project content and meeting history
Tasks API Create, schedule, and run AI-powered tasks programmatically

Domain-Specific

API Description
Meeting Room API Join live meetings and receive real-time transcript events via callbacks

Authentication

Every API request requires an API key. Create one in Sasha Studio:

  1. Click your profile icon and go to My Account
  2. Select the API Tokens tab
  3. Click Create Token and give it a name
  4. Copy the API Key (starts with sk_) and the Signing Secret (starts with ss_)

Include your API key in every request:

# Via X-API-Key header (recommended)
curl -H "X-API-Key: sk_your_key" https://your-sasha.example.com/api/v1/meetings/status

# Via Authorization header
curl -H "Authorization: Bearer sk_your_key" https://your-sasha.example.com/api/v1/meetings/status

Scope: a key sees only what it created. GET /api/v1/meetings/status lists the meetings started under that key — not every meeting of its owner, and not meetings started from the Sasha browser UI. A meeting belonging to another key answers 404 { "error": "Not found" }, the same body as a meeting that does not exist.

Important: The API key and signing secret are only shown once when you create the token. Copy them somewhere safe. If you lose them, you'll need to create a new token.

Reference Client

The fastest way to get started is with the official reference client. It's a small Node.js application that demonstrates the full integration flow — making API calls, receiving callbacks, and verifying HMAC signatures.

Repository: github.com/context-is-everything/sasha-meeting-api-client

git clone https://github.com/context-is-everything/sasha-meeting-api-client.git
cd sasha-meeting-api-client
npm install
node index.js

Open http://localhost:4000 in your browser, enter your Sasha credentials and a meeting URL, and watch live transcription events stream in.

What's Next

  • Tasks API — create tasks, put them on a schedule, or run them on demand
  • Projects API — discover projects and browse meeting history
  • Meeting Room API — full endpoint reference, callback events, and integration guide
  • Integrations — connect Sasha to your existing tools and data sources