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.
ReelspanSwitch from Upload-Post
What you get
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.
Synchronous results per network, request_id for background posts and the status endpoint to poll, with the same success and error shapes.
Idempotency-Key and X-Request-Id work the same way: a repeated request gets the first answer back instead of a second post.
Webhooks keep their format. Only the signature header is named X-Reelspan-Signature; the way to check it is unchanged.
Send to sandbox to run your whole integration end to end, results and webhooks included, without posting anywhere.
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
In Reelspan, create a profile for each Upload-Post user, with the same username, so your requests’ user values still match.
Connect each profile’s accounts, or send your clients a connect link to do it themselves.
Point your client at Reelspan’s API and put a Reelspan API key where the Upload-Post key was.
In code
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.
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]"curl https://api.reelspan.com/v1/posts/status?request_id=$REQUEST_ID \
-H "Authorization: Apikey $REELSPAN_KEY"Move your integration this afternoon.