POSTARD DEVELOPERS

Postard developer documentation

One content workspace. A REST API for your app. MCP tools for your AI client. Start with the interfaces that exist today.

Open docs, private workspaces. These guides need no account. Access to drafts, profiles, and metrics always requires authentication and workspace permission. Customer API keys support scoped draft and profile workflows when a paid plan or trial is active.

What can you build today?

Use the authenticated API to list workspaces, read recent drafts, and save a new text draft. MCP gives authorized AI clients access to the same services, restricted to the workspaces you select.

Instagram and Threads adapters support connection flows and selected metric snapshots after provider configuration. Live access still depends on Meta setup and permissions. A missing metric is reported as unavailable, with no invented performance figures.

The API now includes a private image-upload flow, saved publishing drafts, and scheduling/cancellation endpoints. Live publishing is switched off by default until the worker, provider configuration, and entitlements are ready. Videos, carousels and paid usage overages remain planned. API keys now support scoped workspace, draft and profile actions.

Choose the right endpoint

The Next.js website and Hono API are separate services. Use your configured API origin for REST and append /mcp for MCP. In local development, the website runs on http://localhost:3000 and the API on http://localhost:4000. These local addresses are not a hosted service.

Use https://api.postard.app for REST and https://api.postard.app/mcp for MCP.

Third-party integrations can use a scoped workspace API key once billing is active. The full contract is public, and you can test it against a configured development instance.

Follow the quickstart