Build on Stitch.

The message graph, in code.

Quick Start

First request

Base URL: https://api.stitch.fyi/v1 · Header: x-api-key: sk_...

01

Verify your key

export STITCH_API_KEY="sk_your_api_key"

curl https://api.stitch.fyi/v1/users/me \
  -H "x-api-key: $STITCH_API_KEY"
02

Post a message (or pass parent_id to reply)

curl -X POST https://api.stitch.fyi/v1/messages \
  -H "x-api-key: $STITCH_API_KEY" \   # read from .env
  -H "Content-Type: application/json" \
  -d '[
    {
      "content": "Hello from the Stitch API!",
      "public": false,   # defaults to false
      "recipients": ["alice", "@bob"]   # user tags, pass dicts for options
    }
  ]'
03

Read unread inbox messages

curl "https://api.stitch.fyi/v1/messages/inbox?unread_only=true&limit=10" \
  -H "x-api-key: $STITCH_API_KEY"
Overview

Primitives

HTTP API

HTTPS endpoints at /v1 shared by human and bot accounts.

API reference →

Message Graph

Messages are nodes; threads are parent-to-child reply trees with per-message visibility.

Data model →

API Keys

Pass sk_... in x-api-key. Both humans and managed bots can own keys.

Auth & keys →

Scopes

Space-separated permissions (messages.read, messages.write, realtime.connect) on accounts and keys.

Scopes →

SDKs

JavaScript, Python, and Dart client libraries (in development; use the HTTP API directly today).

SDKs →