Developers

Automate your social presence with the PostMesh Public API, or let an AI agent operate your workspace through the Model Context Protocol (MCP). Everything below reuses the same server-side publish pipeline as the app, so your integration inherits the same validation and never-over-publish guarantees.

Get an API token

Every request is authenticated with a workspace-scoped bearer token. A token belongs to exactly one workspace (team) and can never reach another workspace's data.

1 Sign in and open Settings → API in your workspace.
2 Create a token, choosing the read and/or write abilities it needs.
3 Copy the token (prefix frsk_) — it is shown only once. Store it as a secret.
4 Send it on every request as the Authorization header.

Authorization: Bearer frsk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

The Public API requires a plan that includes API access and an active subscription.

The Public API

A versioned, tenant-isolated REST API under /api/v1. List connected accounts, read and create posts (publish now or schedule), read analytics, and manage webhook subscriptions.

Open the API reference Download the OpenAPI document

Example: list connected accounts

curl https://postmesh.xyz/api/v1/accounts \
  -H "Authorization: Bearer frsk_…"

Supported platforms (no token needed): https://postmesh.xyz/api/v1/platforms

Webhooks

Subscribe an HTTPS endpoint to post.published, post.failed, and account.desynced events. Deliveries are signed with an HMAC-SHA256 signature so you can verify they came from PostMesh.

MCP server (for AI agents)

PostMesh exposes a Model Context Protocol server so an AI agent (Claude and others) can operate your workspace on your behalf. It uses the SAME bearer token as the Public API.

MCP endpoint: https://postmesh.xyz/mcp/postmesh
Discovery descriptor: https://postmesh.xyz/.well-known/mcp.json

Authenticate with Authorization: Bearer frsk_… — the same workspace-scoped token.

Available tools

list_platforms — List each supported network and its publishing capabilities and limits.
list_accounts — List the workspace's connected accounts you can target.
validate_post — Dry-run a proposed post and surface any blockers before writing.
create_draft — Stage a post as an editable draft (nothing is published or queued).
schedule_post — Schedule a post for a future time (never an immediate publish).

The write tools are conservative by design: they only create drafts or future-dated scheduled posts, so an agent can never trigger an immediate publish.