Hashnode's 'free' blog platform quietly paywalled its entire API

Hashnode markets itself as the blogging platform for builders, "free to start," with a public GraphQL API that devs used to automate publishing and pull stats. In June 2026, that API stopped being free. Every request - read or write - now requires a Pro plan per publication. We hit the wall ourselves this week. Here's what changed, what it costs, and where the free line actually sits now.

What Hashnode says

The change is stated plainly, if quietly, on the announcements page:

"We're retiring free GraphQL API access. Every API request, queries and mutations, now requires a Pro plan on your publication." - hashnode.com/announcements/graphql-api

Their reason is abuse:

"Scrapers and spammers were abusing the free API at scale. Read traffic was being used to mirror posts on spam farms. Write traffic was flooding the feed with junk. Both hurt real writers on Hashnode. A small fee filters out abuse and keeps the API usable for everyone."

That's a real problem. Spam farms mirroring posts via the read API is a genuine cost. The fix is what bites.

What it costs

Pro is seat-based, billed per publication. From the in-app Billing page we observed this week (logged into a free publication, US region): $5/month per seat, monthly or yearly (yearly advertised as "2 months free").

The public Introducing Hashnode Pro changelog confirms the model - "pricing is seat-based and adjusts automatically as members join or leave" - though the changelog body does not print the dollar figure; the $5 came from the Billing page we screenshotted. For a solo publication, that's $5/mo to get the API back.

What Pro actually gates

The same changelog lists what moves behind the paywall. The relevant ones for anyone who automates:

• GraphQL API. "Publish and read your publication's content programmatically." (source) - this is the headline. Both reads and writes.
• Headless mode. Use Hashnode as a CMS behind your own frontend.
• Webhooks. Signed requests on publish/update/delete.
• GitHub backup. Mirror posts and drafts to a GitHub repo.
• Bulk markdown import. Bring a publication over from a zip of Markdown files, with frontmatter-mapped titles/tags/canonical URLs/dates.
• Scheduled publishing, custom domains, hide branding, multiple blogs (up to 10 vs. 1 on free), AI assist.

The free tier keeps the editor, one publication, and the public feed. It does not keep programmatic access of any kind.

The part that makes it a CAVEATS

It's not that Hashnode charges for an API. Plenty of platforms do, and the spam-abuse rationale is legitimate. It's the quiet reclassification of a previously-free capability mid-tenancy - and the fact that the API is now gated the same as publishing, so even read-only automation (pull your own stats, mirror your own posts) is paywalled.

For a publication that built workflows on the free API - auto-publishing from a CI job, mirroring posts to another platform, a stats dashboard - those workflows silently broke when the change landed, and the fix is a credit card.

One fair detail worth noting: Hashnode grandfathered publications that had webhooks, a custom domain, or GitHub backup set up before Pro launched - "You keep them. Publications with any of these set up before Pro launched are grandfathered, so nothing changes for you." (source). So the wall hits new and non-configured accounts hardest; existing API users who'd already wired things up before June 2026 are, per Hashnode's word, unaffected. We have not independently verified the grandfathering in practice.

Our receipt

We hit this directly this week. Setting up a new free Hashnode publication (The Free Tier's mirror account), we generated a Personal Access Token from Settings → Developer and called https://gql.hashnode.com. The endpoint 301-redirected to the paywall announcement.

In the dashboard Billing page, "GraphQL API access" and "Bulk markdown import" were both listed under "What Pro includes" at $5/month per seat. The API was unusable without checkout.

That's the receipt: a free publication, a freshly minted PAT, and a redirect to a paywall where the API is listed as a Pro line item.

The verdict

CAVEATS. Hashnode is genuinely free to write on - the editor, one publication, the community feed, no paywall to publish a post by hand. But "free to start" now silently excludes any programmatic access, including reading your own content via the API.

If you automate publishing, mirror posts, run a stats job, or use headless mode, the real price is $5/month per seat, and it arrived as a mid-stream change to something that used to be free.

If you're evaluating Hashnode for an automation-heavy workflow in 2026, budget the $5/seat from day one. If you just want to write posts by hand, the free tier still does that fine - and this change doesn't touch you.

No referral links in this post. Sources linked inline; Hashnode changelog and announcements pages checked July 7, 2026.