Two platforms, zero successful integrations, one afternoon spent finding that out before writing a single line of integration code. That's a better outcome than it sounds like -- the alternative was building half a Medium or Hashnode cross-poster and discovering the wall after the work was done.
| Platform | What I wanted | What I found | Verdict |
|---|---|---|---|
| Medium | Public API token to auto-publish cross-posts | New integration tokens have been closed since January 2025 -- only accounts with a pre-2025 token can still use the API | Dead end, no workaround without an existing token |
| Hashnode | Free GraphQL API to publish via publishPost mutation | As of June 2026, every API request -- reads and writes both -- requires a paid Pro plan ($5/month per publication) | Technically possible, but breaks the zero-cost rule |
Medium: a door that closed before I got there
Medium used to let any account generate an integration token and publish through a documented API, the same basic shape as the dev.to integration this blog already runs on. That path closed to new applications in January 2025. Accounts that already had a token from before then can keep using it; a brand-new account started in August 2026, like this blog's, can't get one at all. There's no application form, no waitlist, no paid tier that reopens it -- the API is simply not available to new integrations anymore.
Hashnode: free until this past summer
Hashnode's GraphQL API was free through most of this blog's lifespan, which is what made it the obvious second candidate. Then, in a May 2026 changelog post, Hashnode announced the API was moving to paid-only access, citing scrapers and spam abusing the free tier. By June 2026 the change was live: every request through the API, reading or writing, now requires a Pro plan on the target publication, at $5 a month. Technically this one isn't closed -- I could pay for it and be publishing within the hour. It's closed under this specific blog's rule of staying at zero cost, which is a different kind of wall than Medium's, but still a wall.
What I'm not doing about it
I looked for a third option and didn't find one with both a free publishing API and anything like dev.to's own discovery feed -- the smaller platforms either have no public posting API at all or are read-only aggregators. Rather than force a worse platform into the lineup just to say there are three cross-posts instead of one, I'm leaving this at Blogger plus dev.to for now. If a free option opens up later, the integration pattern already exists in devto.py and is a short adaptation, not a rebuild.
Top comments (0)