Schedule posts from your own tools and AI agents

Example: posts from an AI chat

A consultant adds the MCP server to Claude. She writes: "Plan 3 LinkedIn posts about our new course for next week and put them in my free slots." Claude lists her channels, finds free slots, checks each post against LinkedIn's rules and schedules them. She sees them on the calendar and edits 1 before it goes out. A webhook tells her CRM when each post is published.

The public API

The REST API follows the Postiz public API paths and bodies, so scripts written for Postiz work after you change the address and the API key. Owners and admins create the key in Settings, Developers. Creating a post accepts an Idempotency-Key header: send the same request twice within 24 hours and you get the first answer back instead of a second post. When you send too many requests, the answer is 429 with a Retry-After header. Every error has a plain message and a fix. The API reference has an example for every endpoint, and the same spec is published as an OpenAPI file.

MCP server and command line

The MCP server lets AI apps like Claude, ChatGPT and Cursor list channels, check a post against each network's rules, find free slots and schedule posts. You paste 1 link into the app's connector settings and sign in; no key to copy. The command line tool does the same from a terminal or a CI server: npm install -g https://postozo.com/downloads/postozo-cli.tgz.

Webhooks and OAuth apps

Webhooks send events, such as a post published or failed, or an approval requested, to your own address. Each message is signed with a sha256 HMAC of the body in the X-Postozo-Signature header, and a failed message is sent again up to 6 times. The last 50 deliveries are kept for 30 days so you can see what happened. If you build a product for other Postozo users, create an OAuth app: your users sign in with Postozo and you get a token for the API, MCP and CLI.

Limits and rules

API, MCP or CLI?

What people build with it

An online shop that posts each new product to Instagram and Facebook from its own system. An agency dashboard that shows every client's scheduled posts in 1 place. A newsroom that publishes breaking news to 6 networks from its content system. A Slack alert for every failed post through a webhook and n8n. A team that plans with Claude and lets it schedule through the MCP server after a human check.

Tips to get more from it

• Read a channel's rules through the API, or use the check_post tool over MCP, before you create posts from a script, so you catch the same problems the editor would show.
• Store the API key as a secret in your automation tool. Rotate it if it ever ends up in a log.
• Use the find free slot tool so posts from scripts and AI apps respect the posting times your team set.

Words on this page, explained

Mistakes to avoid

• Retrying a create call without an Idempotency-Key. Add one so a retry never makes a second post.
• Ignoring Retry-After. Wait the time it says before the next request.
• Not checking the webhook signature. Check it so only real messages from Postozo are trusted.

Who it is for

• Marketing teams connect the calendar to their CRM and reports. See Marketing teams.
• Agencies build their own client dashboards on top of the API. See Agencies.
• Creators schedule posts by talking to their AI app. See Creators.

How other tools handle public API

Of the 12 social media tools we compare, 10 list public API on their own pricing, feature or help pages:

• Postiz: included
• Buffer: Every plan includes API access with monthly request limits (3,000 to 15,000).
• Hootsuite: included
• Sprout Social: The Sprout API is on the Advanced plan.
• Metricool: API access is on Advanced and up.
• SocialPilot: Enterprise plan only.
• Publer: Business plan and up (API and MCP).
• Vista Social: API access is arranged through your Customer Success Manager.
• Planable: Pro plan and up.
• Agorapulse: Custom plan only.

Not confirmed on their own pages: Later and Sendible.

Checked on 29 September 2026 on each tool's official website. Prices and features change, so check before you decide.

Plans and limits

The public API, MCP server and command line tool are in every plan. The number of webhooks grows with the plan. See Pricing for every limit.

Developer docs

The developer docs have the details: the API guide, the API reference with an example for every endpoint, the MCP server tools, webhook events and signatures, the command line tool and OAuth.

Step by step guides for AI apps

Set up the MCP server or the API in the tool you already use:

See all AI agent guides.

Works with these channels

API and MCP works on every connected channel. These are the ones people use it with most:

See all channels, or compare Postozo with other tools on the compare page.