Move from Upload-Post to PostWire in an afternoon

Upload-Post'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 Upload-Post requests for you, in the browser.

What changes, in four lines. The key: Authorization: Bearer pw_live_…. user (a profile's username, in the form) 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.

Upload-Post'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

Upload-Post: POST https://api.upload-post.com/api/upload (video), /api/upload_photos, /api/upload_text. PostWire: POST https://postwire.io/api/post (now) or POST https://postwire.io/api/schedule (later).

Upload-PostPostWireNotes
titledocs.upload-post.com, Oct 9, 2026text (and title for YouTube)Upload-Post's title is the caption and YouTube's default title.
platform[]docs.upload-post.com, Oct 9, 2026platformsSame names (x, tiktok, instagram…).
userdocs.upload-post.com, Oct 9, 2026brand_idOne brand per client.
video (file or URL)docs.upload-post.com, Oct 9, 2026video_urlPostWire takes a public URL; upload local files with POST /api/media/upload-url.
photos[] (files or URLs)docs.upload-post.com, Oct 9, 2026media[].url (or photo_url)
descriptiondocs.upload-post.com, Oct 9, 2026per_platform.youtube.text / per_platform.linkedin.textThe longer text for YouTube, LinkedIn and Facebook.
<platform>_titledocs.upload-post.com, Oct 9, 2026per_platform.<network>.text (youtube_title → title)
first_commentdocs.upload-post.com, Oct 9, 2026per_platform.<network>.first_commentPostWire: LinkedIn, X, Bluesky, Mastodon.
scheduled_date (+ timezone)docs.upload-post.com, Oct 9, 2026run_at (POST /api/schedule)Send the offset in run_at (e.g. -05:00) instead of a separate timezone.
Idempotency-Key (header)docs.upload-post.com, Oct 9, 2026idempotency_key (body)24 hours on PostWire.

Network names: tiktok → tiktok · instagram → instagram · linkedin → linkedin · youtube → youtube · facebook → facebook · x → x · bluesky → bluesky · mastodon → mastodon · discord → discord · telegram → telegram · threads → not offered by PostWire · pinterest → not offered by PostWire · reddit → not offered by PostWire · google_business → not offered by PostWire.

The same post, side by side

Upload-Post — their docs' example

curl \
  -H 'Authorization: Apikey your-api-key-here' \
  -F 'video=@/path/to/your/video.mp4' \
  -F 'title="Your Video Title"' \
  -F 'user="test"' \
  -F 'platform[]=tiktok' \
  -X POST https://api.upload-post.com/api/upload

From docs.upload-post.com, read Oct 9, 2026.

PostWire — REST (the converter's output)

curl -X POST https://postwire.io/api/post \
  -H "Authorization: Bearer $POSTWIRE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "platforms": [
    "tiktok"
  ],
  "text": "Your Video Title"
}'

your key from the pasted command is not carried over: the output uses $POSTWIRE_API_KEY video @/path/to/your/video.mp4 is a local file: upload it (POST /api/media/upload-url) and pass its URL as video_url user (an Upload-Post profile) → 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

PostWire — n8n node

PostWire node
  Resource:   Post
  Operation:  Publish
  Networks:   tiktok
  Content:    Same Text on Every Network
  Text:       Your Video Title
  Options → Brand: the client's brand

PostWire — MCP (Claude, ChatGPT, any agent)

post_to_social({
  "platforms": [
    "tiktok"
  ],
  "text": "Your Video Title"
})

# or ask your agent: "Post this on TikTok"

What changes

Upload-PostPostWire
AuthenticationAuthorization: Apikey your-api-key-here (multipart form, not JSON)docs.upload-post.com, Oct 9, 2026Authorization: Bearer pw_live_… — an API key from the dashboard; the MCP server also signs in with OAuth 2.1
One clientuser (a profile's username, in the form)docs.upload-post.com, Oct 9, 2026brand_id — one brand per client, its networks connected once (GET /api/brands lists them)
Schedulingscheduled_date (ISO 8601) and an optional IANA timezone; add_to_queue for a queue slotdocs.upload-post.com, Oct 9, 2026POST /api/schedule with run_at (ISO 8601 with offset) or "next_slot", checked at queue time
Webhooksupload_completed, social_account_connected, social_account_disconnected, social_account_reauth_requireddocs.upload-post.com, Oct 9, 2026post.published, post.failed, connection.reauth_required — one per network, signed (PostWire-Signature, HMAC-SHA256), retried for two days
Retries without duplicatesIdempotency-Key header: a matching job returns the existing onedocs.upload-post.com, Oct 9, 2026idempotency_key (24 hours); an identical post is refused for 2 minutes even without one
Checking a postGET /api/uploadposts/status?request_id=… or ?job_id=…docs.upload-post.com, Oct 9, 2026GET /api/post/status, or the webhook

Convert your Upload-Post requests

Paste a cURL command or a JSON body from your code. The PostWire request comes out, ready to run.

Networks, when the request only has account or channel IDs

Runs in your browser: no AI, no server, nothing you paste or upload leaves this page. Try it free

Move in an afternoon

  1. Open a PostWire account (free, no card) and create an API key under API & MCP.
  2. Create one brand per client — POST /api/brands or the dashboard. It takes the place of Upload-Post's user.
  3. Connect each client's networks: POST /api/connect-link returns 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.
  4. Swap the base URL and the auth header in your code: https://postwire.io/api/ and Authorization: Bearer pw_live_….
  5. Convert your requests with the converter above (or by the field table), and send brand_id with each one.
  6. Move the queue: list what is still scheduled on Upload-Post and re-create it with POST /api/schedule, or as one CSV under Automate → Bulk upload (checked row by row before anything is scheduled).
  7. Point your webhook receiver at PostWire: POST /api/webhooks with your URL, and verify PostWire-Signature.
  8. Send one real post to one network and watch GET /api/post/status or the webhook.
  9. When the Upload-Post 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 Upload-Post

  • Every network's post written from a text idea, in the same request: TikTok caption, Instagram caption, YouTube title, description and tags, LinkedIn post, Bluesky under 300 characters. Upload-Post's AI writes the title, description and hashtags starting from a video, for YouTube, Instagram and TikTok (its pricing page, Oct 9, 2026).
  • TikTok on the free plan. Upload-Post's free plan (2 profiles, 10 uploads a month) does not include TikTok.
  • Links stay in X posts. A post with a link uses 10 of the X credits every paid plan includes. Upload-Post removes links from X posts unless you pay +$19 a month.

Questions people ask

How long does it take to move from Upload-Post 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 Upload-Post 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 Upload-Post's user (a profile's username, in the form)?

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 Upload-Post?

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 Upload-Post?

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 Upload-Post 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.