Migrate from Upload-Post

Reelspan takes the same request shapes as Upload-Post: the same form fields (user, platform[], title, scheduled_date, async_upload, {platform}_title and the rest), the same per-network results in the answer, and webhooks with the same event names and payloads. Most integrations move by changing the base URL, the key and the paths.

1. Change the base URL and the key

Reelspan reads both schemes, so the header can stay as it is: only the key changes. Create a key in the dashboard under Developers → API keys; see Authentication.

curl -X POST https://api.reelspan.com/v1/posts/video \
  -H "Authorization: Bearer $REELSPAN_API_KEY" \
  -F "user=my-brand" \
  -F "platform[]=tiktok" \
  -F "platform[]=youtube" \
  -F "title=Launch day" \
  -F "[email protected]"

2. Change the paths

Paths drop the /uploadposts prefix and use /v1/... names. Bodies and query parameters stay the same unless a note says otherwise.

Publishing

Scheduling and the queue

Profiles and accounts

Lookups and analytics

Webhooks

3. Fields and headers that differ

The rest carry over as they are: the X-Request-Id and X-External-Id headers (Retrying safely), the gbp_* Google Business fields including EVENT and OFFER posts, facebook_media_type=VIDEO, and PDF, PPT, PPTX, DOC and DOCX documents.

Network fields that Reelspan doesn't read are ignored, not refused, so check each network's page under Networks for the fields it takes.

4. Update your webhook receiver

Event names (upload_completed, social_account_connected, social_account_disconnected, social_account_reauth_required) and payloads are the same; dotted spellings such as social_account.connected are accepted when you subscribe. The headers are renamed, and the signature is built the same way, an HMAC-SHA256 of "{timestamp}.{raw body}":

Register the endpoint again on Reelspan: it gets a new signing secret (whsec_…). Reelspan sends webhooks only; there is no Telegram notification channel. See Webhooks.

What you get on top

• Test keys and a sandbox network. A rs_test_ key runs every check and publishes nothing; the sandbox network needs no connected account. See Test mode.
• Upload once, post many times. Upload media returns a media_id to use as video_media_id, photo_media_ids[], thumbnail_media_id or cover_media_id, and files over 100 MB go straight to storage in parts.
• Repeats. repeat_every (day, week, month) and repeat_times schedule a whole series at once; DELETE /v1/scheduled/{job_id}?series=rest cancels the rest of it.
• Finer retries. Retry can send only some networks again, change their settings first, and run now or at a set time.
• Webhook deliveries you can see. Failed deliveries are retried with backoff, every delivery is in a log, and you can redeliver one or send a test event.
• Approval links. Send scheduled posts to a client, who approves each one from a link before it goes out. See Approval links.
• More analytics. Daily account history, best times to post and period reports.
• Official SDKs for Node.js and Python with retries and idempotent posts built in. See SDKs.

Not available yet

These Upload-Post endpoints have no Reelspan equivalent today: TikTok hashtag suggestions; comments, DMs and AutoDMs; cached bulk post analytics; Google Business location info and reviews. Editing or unpublishing YouTube videos and Threads posts isn't possible either: Unpublish and Edit a post list the networks that work. If your integration depends on one of these, tell us.