01
Connect X
- In the dashboard, open Accounts and pick X.
- Sign in with X and allow Reelspan to post.
- The account joins the profile you had open; every post to that profile can now include it.
Posting for clients? Send them a connect link so they connect their own X account without a Reelspan login.
02
Get an API key
In the dashboard, open Developers → API keys and create one. Keep it in an environment variable such as REELSPAN_KEY; never in code you share.
03
Post with one request
Send the video as a file, or as a public URL like below. Add more platform[] fields to post the same thing everywhere at once.
curl -X POST https://api.reelspan.com/v1/posts/video \
-H "Authorization: Bearer $REELSPAN_KEY" \
-F user=my-brand \
-F "platform[]=x" \
-F "video=https://example.com/clip.mp4" \
-F "title=Your post" \
-F "reply_settings=…"const form = new FormData();
form.append('user', 'my-brand');
form.append('platform[]', 'x');
form.append('video', 'https://example.com/clip.mp4');
form.append('title', 'Your post');
const res = await fetch('https://api.reelspan.com/v1/posts/video', {
method: 'POST',
headers: { Authorization: `Bearer ${process.env.REELSPAN_KEY}` },
body: form,
});
console.log(await res.json());import os, requests
res = requests.post(
"https://api.reelspan.com/v1/posts/video",
headers={"Authorization": f"Bearer {os.environ['REELSPAN_KEY']}"},
files=[
("user", (None, "my-brand")),
("platform[]", (None, "x")),
("video", (None, "https://example.com/clip.mp4")),
("title", (None, "Your post")),
],
)
print(res.json())x_title sets the text for X only, when it should differ from the other networks’.
04
X options
- x_title
- The post text for X; longer text becomes a thread.
- reply_settings
- Limit replies: following, mentionedUsers, subscribers or verified.
- poll_options
- A poll of 2 to 4 options.
- x_quote_tweet_id
- Quote another post.
- alt_text
- Alt text for photos.
- Longer text is split into a thread for you.
- Choose who can reply, and add alt text to photos.
Every field, with its limits: the docs.
05
Schedule it and check the result
- Add
scheduled_date(ISO 8601) andtimezoneto post later, oradd_to_queue=trueto take the next slot of your posting schedule. - The response has X’s status and the post’s link. For big files send
async_upload=trueand checkGET /v1/posts/status?request_id=…, or get a signed webhook when it’s live. - If X refuses a post, the error says why in plain words, and you can retry just that network.
06
Without code
07
Ideas
- Turn a long announcement into a thread automatically.
- Post release notes from GitHub Actions.
More on X: what you can post there. Other networks: all upload guides.