The hosted Postiz alternative for AI agents and developers

The decision is not features. It is who runs the thing.

If you are comparing Postiz with a hosted social media API, the feature checklists will mostly agree: both publish and schedule to the big networks, both handle media, both have an API and an MCP server. The real question is who carries the burden. Self-hosting means you own the Docker Compose file, the Postgres instance, the Redis queue, the upgrade path, and every platform OAuth app - including the Meta app review that can take weeks before a single Instagram account connects.

A hosted API trades that control for time. You lose the ability to fork the code and keep every byte on your own disks; you gain a system that already has approved platform apps, retries, and someone else on call. We wrote the long version of this trade-off in self-hosted vs a hosted social media API.

Mapping the Postiz public API to Outstand

Postiz's public API lives at https://api.postiz.com/public/v1 and authenticates with your API key in a bare Authorization header. Outstand lives at https://api.outstand.so/v1 and uses Authorization: Bearer YOUR_API_KEY. Endpoint by endpoint:

Listing connected channels

# Postiz
curl -X GET https://api.postiz.com/public/v1/integrations \
  -H "Authorization: YOUR_POSTIZ_API_KEY"

# Outstand
curl -X GET https://api.outstand.so/v1/social-accounts \
  -H "Authorization: Bearer YOUR_API_KEY"

Publishing a post

Postiz targets specific integration ids. Outstand's accounts array accepts an account id from GET /v1/social-accounts, or an account's exact username, and resolves each identifier to the matching connected accounts - so a single call can fan out across networks.

# Outstand - publish now to X and LinkedIn
curl -X POST https://api.outstand.so/v1/posts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "containers": [{ "content": "Our Q2 launch is live" }],
    "accounts": ["YOUR_X_ACCOUNT_ID", "YOUR_LINKEDIN_ACCOUNT_ID"]
  }'

Add an ISO 8601 scheduledAt to schedule instead of publishing immediately. Media is attached per container as { url, filename } using the public URL returned by the confirm-upload step.

Cancelling a scheduled post

# Postiz
curl -X DELETE https://api.postiz.com/public/v1/posts/POST_ID \
  -H "Authorization: YOUR_POSTIZ_API_KEY"

# Outstand
curl -X DELETE https://api.outstand.so/v1/posts/POST_ID \
  -H "Authorization: Bearer YOUR_API_KEY"

The one step that is not a find-and-replace: reconnecting accounts. OAuth tokens issued under your own Postiz platform apps cannot be moved, so every account is authorized once more through Outstand. On the networks with managed apps that is a redirect and a click - no developer app, no review queue. See pricing to sanity-check the per-post math against your current infra bill.