ReelspanUpload guidesHashnode

Post to Hashnode automatically

Connect Hashnode once, then send text posts to it from code, a workflow or an AI agent. The same call can post to every other network at the same time.
1 min setup100,000 characters16:97 sections

01

Connect Hashnode

  1. On Hashnode, open Account settings → Developer → Generate new token.
  2. Paste it in the dashboard, with the blog if you have more than one.

Posting for clients? Send them a connect link so they connect their own Hashnode 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

Add more platform[] fields to post the same thing everywhere at once.

curl
curl -X POST https://api.reelspan.com/v1/posts/text \
  -H "Authorization: Bearer $REELSPAN_KEY" \
  -F user=my-brand \
  -F "platform[]=hashnode" \
  -F "title=Your article (markdown)" \
  -F "hashnode_tags=…"
JavaScript (Node 18+)
const form = new FormData();
form.append('user', 'my-brand');
form.append('platform[]', 'hashnode');
form.append('title', 'Your article (markdown)');

const res = await fetch('https://api.reelspan.com/v1/posts/text', {
  method: 'POST',
  headers: { Authorization: `Bearer ${process.env.REELSPAN_KEY}` },
  body: form,
});
console.log(await res.json());
Python
import os, requests

res = requests.post(
    "https://api.reelspan.com/v1/posts/text",
    headers={"Authorization": f"Bearer {os.environ['REELSPAN_KEY']}"},
    files=[
        ("user", (None, "my-brand")),
        ("platform[]", (None, "hashnode")),
        ("title", (None, "Your article (markdown)")),
    ],
)
print(res.json())

hashnode_title sets Hashnode’s title (up to 250 characters), separate from the text.

04

Hashnode options

hashnode_title
The article title.
hashnode_tags
Up to 5 tags, comma-separated.
hashnode_canonical_url
Where the article first ran.
  • Articles in Markdown on your Hashnode blog.
  • Set tags and a canonical URL when the article first ran elsewhere.

Every field, with its limits: the docs.

05

Schedule it and check the result

  • Add scheduled_date (ISO 8601) and timezone to post later, or add_to_queue=true to take the next slot of your posting schedule.
  • The response has Hashnode’s status and the post’s link. For big files send async_upload=true and check GET /v1/posts/status?request_id=…, or get a signed webhook when it’s live.
  • If Hashnode refuses a post, the error says why in plain words, and you can retry just that network.

06

Without code

07

Ideas

  • Publish the same Markdown article to Hashnode and Dev.to at once.

More on Hashnode: what you can post there. Other networks: all upload guides.

Questions?Talk to a person.Contact us