Move from Postiz to PostWire in an afternoon
Postiz's publish request, mapped field by field to PostWire's, with the same post side by side as cURL, an n8n node and an MCP call — and a converter that rewrites your Postiz requests for you, in the browser.
Authorization: Bearer pw_live_…. posts[].integration.id (a channel); customers are groups becomes brand_id, one brand per client. Scheduling: POST /api/schedule with run_at. And one thing PostWire adds: POST /api/generate writes each network's post from one idea before you publish.Postiz's fields read on its own docs on Oct 9, 2026, linked on each row; PostWire's checked against openapi.json when this page was built.
Field by field
Postiz: POST https://api.postiz.com/public/v1/posts. PostWire: POST https://postwire.io/api/post (now) or POST https://postwire.io/api/schedule (later).
| Postiz | PostWire | Notes |
|---|---|---|
type: "now"docs.postiz.com, Oct 9, 2026 | POST /api/post | Publish immediately. |
type: "schedule" + datedocs.postiz.com, Oct 9, 2026 | POST /api/schedule with run_at | UTC ISO 8601 in both. |
posts[].integration.iddocs.postiz.com, Oct 9, 2026 | platforms + brand_id | Postiz's channel ID; PostWire takes the network name, inside the client's brand. |
posts[].settings.__typedocs.postiz.com, Oct 9, 2026 | platforms[] | The provider name becomes the network name (x, instagram, linkedin…). |
posts[].value[0].contentdocs.postiz.com, Oct 9, 2026 | text / per_platform.<network>.text | One text per channel on Postiz; PostWire takes one shared text plus overrides. |
posts[].value[0].image[].pathdocs.postiz.com, Oct 9, 2026 | media[].url | Postiz wants files uploaded to it first; PostWire takes any public URL. |
posts[].value[1..]docs.postiz.com, Oct 9, 2026 | per_platform.<network>.thread | Thread posts, for X, Bluesky and Mastodon. |
posts[].settings.title (YouTube)docs.postiz.com, Oct 9, 2026 | title | |
shortLink, tagsdocs.postiz.com, Oct 9, 2026 | — | No equivalent: links stay as written; labels go in the dashboard. |
Network names: x → x · linkedin → linkedin · linkedin-page → not offered by PostWire · facebook → facebook · instagram → instagram · instagram-standalone → instagram · threads → not offered by PostWire · bluesky → bluesky · mastodon → mastodon · youtube → youtube · tiktok → tiktok · discord → discord · telegram → telegram · reddit → not offered by PostWire · pinterest → not offered by PostWire.
The same post, side by side
Postiz — their docs' example
curl -X POST "https://api.postiz.com/public/v1/posts" \
-H "Authorization: your-api-key" \
-H "Content-Type: application/json" \
-d '{
"type": "schedule",
"date": "2024-12-14T10:00:00.000Z",
"shortLink": false,
"tags": [],
"posts": [{
"integration": { "id": "your-instagram-id" },
"value": [{
"content": "Beautiful sunset #photography",
"image": [{ "id": "img-123", "path": "https://uploads.postiz.com/photo.jpg" }]
}],
"settings": {
"__type": "instagram",
"post_type": "post"
}
}]
}'From docs.postiz.com, read Oct 9, 2026.
PostWire — REST (the converter's output)
curl -X POST https://postwire.io/api/schedule \
-H "Authorization: Bearer $POSTWIRE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"platforms": [
"instagram"
],
"text": "Beautiful sunset #photography",
"photo_url": "https://uploads.postiz.com/photo.jpg",
"run_at": "2024-12-14T10:00:00.000Z"
}'your key from the pasted command is not carried over: the output uses $POSTWIRE_API_KEY integration.id (a Postiz channel) → brand_id: create one PostWire brand per client (POST /api/brands) and send its id; with a single brand you can leave brand_id out the media is hosted by Postiz: pass a URL you host, or upload it to PostWire (POST /api/media/upload-url) run_at is in the past: PostWire refuses a schedule in the past — set a future time
PostWire — n8n node
PostWire node Resource: Post Operation: Schedule Networks: instagram Content: Same Text on Every Network Text: Beautiful sunset #photography Media URL: https://uploads.postiz.com/photo.jpg When: At a Specific Time Publish At: 2024-12-14T10:00:00.000Z Options → Brand: the client's brand
PostWire — MCP (Claude, ChatGPT, any agent)
schedule_post({
"platforms": [
"instagram"
],
"text": "Beautiful sunset #photography",
"photo_url": "https://uploads.postiz.com/photo.jpg",
"run_at": "2024-12-14T10:00:00.000Z"
})
# or ask your agent: "Schedule this on Instagram for 2024-12-14T10:00:00.000Z"What changes
| Postiz | PostWire | |
|---|---|---|
| Authentication | Authorization: your-api-key (the raw key, no Bearer)docs.postiz.com, Oct 9, 2026 | Authorization: Bearer pw_live_… — an API key from the dashboard; the MCP server also signs in with OAuth 2.1 |
| One client | posts[].integration.id (a channel); customers are groupsdocs.postiz.com, Oct 9, 2026 | brand_id — one brand per client, its networks connected once (GET /api/brands lists them) |
| Scheduling | type now | schedule | draft, with date (UTC ISO 8601)docs.postiz.com, Oct 9, 2026 | POST /api/schedule with run_at (ISO 8601 with offset) or "next_slot", checked at queue time |
| Webhooks | A webhook fired when a post publishes, set up in the app (Settings); its payload is not documenteddocs.postiz.com, Oct 9, 2026 | post.published, post.failed, connection.reauth_required — one per network, signed (PostWire-Signature, HMAC-SHA256), retried for two days |
| Retries without duplicates | Not listed | idempotency_key (24 hours); an identical post is refused for 2 minutes even without one |
| Checking a post | GET /posts?startDate&endDate: state QUEUE, PUBLISHED, ERROR or DRAFTdocs.postiz.com, Oct 9, 2026 | GET /api/post/status, or the webhook |
Convert your Postiz requests
Paste a cURL command or a JSON body from your code. The PostWire request comes out, ready to run.
Move in an afternoon
- Open a PostWire account (free, no card) and create an API key under API & MCP.
- Create one brand per client —
POST /api/brandsor the dashboard. It takes the place of Postiz's posts[].integration.id. - Connect each client's networks:
POST /api/connect-linkreturns a one-hour link the client opens to sign in to each network. TikTok, Meta and Google approvals are PostWire's, so there is no app review on your side. - Swap the base URL and the auth header in your code:
https://postwire.io/api/andAuthorization: Bearer pw_live_…. - Convert your requests with the converter above (or by the field table), and send
brand_idwith each one. - Move the queue: list what is still scheduled on Postiz and re-create it with
POST /api/schedule, or as one CSV under Automate → Bulk upload (checked row by row before anything is scheduled). - Point your webhook receiver at PostWire:
POST /api/webhookswith your URL, and verifyPostWire-Signature. - Send one real post to one network and watch
GET /api/post/statusor the webhook. - When the Postiz queue is empty, cancel that plan. PostWire's paid plans have a 14-day refund if it is not for you.
Where PostWire is ahead of Postiz
- A free hosted plan, no card, no time limit, with the API and MCP. Postiz's hosted plans start at $29 a month after a 7-day trial.
- No server and no app reviews to run. TikTok Direct Post (Jul 7, 2026) and Meta (Jul 14, 2026) are approved for PostWire's apps; you connect with one click. Self-hosting Postiz means your own developer apps, so TikTok's audit and Meta's review are yours to pass.
Questions people ask
How long does it take to move from Postiz to PostWire?
An afternoon for most integrations: the request maps field by field (the table on this page), the auth header and the client key change, and the converter on this page turns Postiz requests into PostWire's. Connecting each client's networks is one sign-in per network, from a link you can send the client.
What replaces Postiz's posts[].integration.id (a channel); customers are groups?
A brand: one per client business, each with its own connected networks. Send brand_id with the post (GET /api/brands lists them); a key that only has one brand can leave it out.
Does PostWire have webhooks and idempotency like Postiz?
PostWire signs every webhook (PostWire-Signature: HMAC-SHA256) and sends post.published, post.failed and connection.reauth_required, one per network, retried for two days. An identical post is refused for 2 minutes, or for 24 hours when you send your own idempotency_key.
Can I try PostWire before cancelling Postiz?
Yes. The free plan has the REST API and the MCP server (1 business, 20 posts a month, no card), and Pro has a 7-day free trial; run both side by side until your queue on Postiz is empty.
Type one idea and see the post each network gets.
The demo on the home page writes live, with no account, and never publishes. The free plan covers one business — every network connects free, 2 networks per post — with no card and no time limit. Paid plans have a 14-day refund.