OrbitwriteDocs

Build on Orbitwrite

Everything the app can do, you can do from code or an AI agent, through one API with the same rules.

Orbitwrite is API-first. The web app is one client of https://orbitwrite.com/api/v1; the MCP server, the CLI and the SDK are others. They all go through the same permission checks, the same platform limits and the same approvals, so a post made from a script behaves exactly like one made in the app.

Pick a surface

MCP server

Connect Claude, ChatGPT, Cursor or any MCP client to your workspace.

CLI

Post, plan and work the inbox from a terminal or a CI job.

TypeScript SDK

A typed client for posts, schedules, the inbox and analytics.

HTTP API

Every endpoint, with a playground.

Webhooks

Get told when posts publish, fail or need review.

Agent skill

Teach your coding agent how Orbitwrite works.

Start here

  1. Get a credential: an API key from Settings → API keys, or sign in with OAuth.
  2. Follow the quickstart to schedule a post with curl.
  3. Read the platform rules for what each network accepts.

Concepts you'll meet

  • Workspace (organizationId): everything is scoped to one. An API key belongs to exactly one workspace.
  • Channel (accountId): a connected account on a network. List them with GET /api/v1/connected-accounts.
  • Post (groupId): one post across one or more channels. On the wire it's a composer group of per-channel rows, and every post operation takes the groupId.
  • Times are ISO 8601 instants in UTC, such as 2026-10-01T09:00:00Z.

Available on every plan

The API, MCP server, CLI and SDK are included on every plan. What a credential can do is decided by its permissions; what a workspace can do (inbox, webhooks, approvals) by its plan.