Postiz alternative (API-only)

Postiz calls itself "the agentic social media scheduler": agents or people plan, generate and schedule posts, and a human reviews them in a visual calendar before they publish. Its homepage names three audiences: AI-first marketers prompting Claude or ChatGPT, developers building on its OAuth2, SDK and public API, and automation teams using n8n or Make.

The codebase is open source under AGPL-3.0 and on GitHub. You can self-host it with Docker for free, but you run the server, updates and backups, and you get your own app approvals from each social network. The pricing FAQ says the hosted platform is where agent features ship first and self-hosting is a secondary option.

All prices below were read on postiz.com/pricing on 2026-11-01. Every plan has unlimited posts, a 7-day free trial, and the MCP server, CLI, API and webhooks. Annual billing saves about 20% and isn't refundable.

• Standard: $29/mo ($23/mo yearly). 5 channels, no team members, no AI images, 3 AI videos and 60 clipping minutes a month.
• Team: $39/mo ($31 yearly). 10 channels, unlimited team members, 100 AI images, 10 AI videos, 120 clipping minutes.
• Pro: $49/mo ($39 yearly). 30 channels, 300 AI images, 30 AI videos, 300 clipping minutes.
• Ultimate: $99/mo ($79 yearly). 100 channels, 500 AI images, 60 AI videos, 600 clipping minutes.
• On every plan: picture editor, AI copilot, comments, repeated posts, RSS auto-post, analytics, customer groups, calendar views, signatures.

The public API lives at https://api.postiz.com/public/v1. You send the key from your settings in the Authorization header with no Bearer prefix, or an OAuth2 token starting pos_ when your app acts for other Postiz users. A connected account is a "channel" in the UI and an "integration" in the API: GET /integrations lists them, POST /upload takes images as multipart form data, and POST /posts creates a post with type (now or schedule), a date, and a posts array with one entry per integration.

The create-post endpoint is limited to 90 requests an hour (100 on cloud). The docs say the limit is one global value per instance, doesn't vary by plan, and self-hosters can change it with API_LIMIT. Agents can also connect through the hosted MCP server (API key or OAuth token as a Bearer token), the Postiz CLI, or an installable skill.

Platform coverage is the biggest gap. Postiz posts to Instagram, TikTok, YouTube, Threads, Facebook, Pinterest and more today. We have five networks live: X, Bluesky, LinkedIn (personal profiles), Mastodon and Telegram. The rest are coming. If you need those networks this month, use Postiz.

Postiz also has a calendar where a person approves what an agent drafted, AI media generation, team roles, and a self-hosted edition you can run on your own servers. We have none of these. If a human reviews every post in a UI, that review step is the product, and Postiz has it. For a simpler scheduler app, Post Bridge is the other option.

Pricing unit. Postiz charges by connected channels in tiers. We charge by accounts that published that month, so ten client accounts that sit idle in October cost nothing. At 3 accounts we're $0 on Free; at 25 we're $29 against Postiz's $49; at 100 Postiz's $99 is close to our $79. The full math is on pricing.

Preflight and receipts. Every post runs plain-code checks before it's sent (length per network, media count, duplicates in the last 24 hours, daily caps, accounts flagged for reconnection) and fails with a 422 that lists each issue with a fix. Each target account gets its own status, URL, attempt count and error, and retryable failures retry on a fixed schedule (30s, 2m, 10m, 30m, 2h). Idempotency keys are accepted on every create.

Agents. Our MCP server is on the Free plan too, so you can wire it into Claude Code before paying anything. For X, we warn when a post contains a link, because X charges more for those (see X API pricing).

The endpoints differ, but the concepts map one to one. A Postiz integration is one of our accounts: GET /public/v1/integrations becomes GET /v1/accounts. A Postiz post with several entries in posts becomes one POST /v1/posts with several ids in accounts; per-network text goes in platform_options. type: "now" is the default when you omit scheduled_at. Instead of uploading to /upload first, pass public image URLs in media. Customer groups map to external_ref on connect links, and GET /v1/accounts?external_ref=client_42 lists one client's accounts.

Your users reconnect their accounts through our connect links, since OAuth grants don't transfer between apps. The docs cover the full request and response.

# One Postiz post to two integrations becomes one call with two account ids
curl -X POST https://socialsforai.com/v1/posts \
  -H "Authorization: Bearer $SOCIALS_KEY" \
  -H "Idempotency-Key: launch-2026-11-03" \
  -H "Content-Type: application/json" \
  -d '{
    "accounts": ["acc_bluesky", "acc_linkedin"],
    "text": "We shipped v2. Notes: https://example.com/v2",
    "media": [{ "url": "https://example.com/v2.png", "type": "image", "alt": "v2 screenshot" }],
    "scheduled_at": "2026-11-03T15:00:00Z"
  }'