ReelspanSwitch from Upload-Post

Moving from Upload-Post? Keep your code.

Reelspan reads the same fields, accepts the same Apikey header and answers in the same shapes. Point your integration at Reelspan, swap the key, and your posts keep going out.
Same field namesSame Apikey header14 days of Pro free

What you get

Fields

Your requests, as they are

user, title, platform[], the video or photos, scheduled_date and each network’s own options: Reelspan accepts Upload-Post’s names, and its own where they differ.

Answers

The same answers back

Synchronous results per network, request_id for background posts and the status endpoint to poll, with the same success and error shapes.

Retries

Safe to send twice

Idempotency-Key and X-Request-Id work the same way: a repeated request gets the first answer back instead of a second post.

Webhooks

Signed like before

Webhooks keep their format. Only the signature header is named X-Reelspan-Signature; the way to check it is unchanged.

Testing

A network that posts nothing

Send to sandbox to run your whole integration end to end, results and webhooks included, without posting anywhere.

Extras

What you get on top

A dashboard with a calendar, queue and bulk scheduling, client approval links, branded reports, and one-click retries of a failed network.

How it works

  1. 1

    Create the same profiles

    In Reelspan, create a profile for each Upload-Post user, with the same username, so your requests’ user values still match.

  2. 2

    Connect the networks

    Connect each profile’s accounts, or send your clients a connect link to do it themselves.

  3. 3

    Change the address and the key

    Point your client at Reelspan’s API and put a Reelspan API key where the Upload-Post key was.

In code

The same request, a new address

The fields stay as they are. Your client sends them to Reelspan’s endpoint with a Reelspan key; the Apikey header Upload-Post clients use works too. Every endpoint is in the API reference.

Post a video
curl -X POST https://api.reelspan.com/v1/posts/video \
  -H "Authorization: Apikey $REELSPAN_KEY" \
  -F "user=firestack" \
  -F "title=Why your phone gets hot" \
  -F "platform[]=tiktok" \
  -F "platform[]=youtube" \
  -F "platform[]=instagram" \
  -F "[email protected]"
Check a background post
curl https://api.reelspan.com/v1/posts/status?request_id=$REQUEST_ID \
  -H "Authorization: Apikey $REELSPAN_KEY"

Move your integration this afternoon.