postmatic

What does not exist yet

The honest list of what the API does not do today, the workaround while it is missing, and the order in which we intend to deliver.

We would rather you find out here than in production. This page lists what the API does not do today. The order below is the planned delivery order, subject to change.

Other platforms

Instagram only, through Instagram Login. Next under study are Threads and Facebook (same Meta app) and LinkedIn. The platform parameter already exists in the routes so that expansion does not change the contract.

Post lifecycle

  • Drafts: a post cannot be saved without publishing or scheduling.
  • Editing: caption, images and accounts do not change after creation. Only the time, through PATCH /v1/posts/:id. To change the rest, cancel and create another.
  • Cancelling becomes failed: a cancelled post stays in the history as failed with errorCode: CANCELLED; it does not go back to draft.

Accounts and profiles

  • An account cannot be moved from one profile to another, and a profile cannot be read or edited individually.
  • No BYOK (connecting accounts under your own Meta app). appId is accepted and ignored.
  • No "headless" account selection: the connect flow is always Meta's.

Account and billing

  • No plans, credits or billing. There is no GET /v1/usage.
  • One organization per user, no invitations and no roles beyond owner.
  • API keys without scopes: every key has full access to the project.
  • No sandbox environment.

Media

  • No automatic expiry and no route to delete uploaded images or videos.

Tooling

No official SDK, MCP server or CLI. The OpenAPI spec lets you generate a client in your language today; the index for agents is at /llms.txt.

What does not exist yet — Postmatic Documentation