Postika developer docs
Postika schedules and publishes posts on eight social networks. Connect your own AI over MCP, call the REST API from your code, or let other Postika users authorize your product with OAuth.
Three ways to integrate
All three run on the same engine and the same rules: what an AI can do over MCP, your code can do over the REST API.
Core concepts
| Object | What it is |
|---|---|
| project | A brand or app with its own channels, calendar and time zone. API keys belong to one project; OAuth tokens reach every project of the user. |
| channel | A connected social account (Instagram, X, LinkedIn…) inside a project, with its own character limit and media rules. |
| post | Text sent to one or more channels. It can be a draft, pending approval, scheduled, or published right away. |
Every date is written in the project's local time as YYYY-MM-DD HH:MM. You never deal with UTC offsets: 2026-11-12 09:30 means 09:30 where the project lives.
Posts created with mode: "approval" wait in the app until a person approves them. It is the safest way to let an agent write for you, and the mode the MCP server suggests to AIs by default.
Base URL
All endpoints live on the same host:
REST API https://postika.app/api/v1
MCP server https://postika.app/api/mcp
OAuth https://postika.app/oauth/authorize · https://postika.app/api/oauth/tokenReady to try it? Follow the Quickstart: connecting Claude takes a minute.