The gap after the shutdown
Thousands of apps depended on Medium’s API. When it went away, teams either maintained fragile scrapers or trusted opaque proxies. Neither scales when you have customers counting on you.
About Zenndra
When Medium retired their official API, developers were left with scrapers, broken wrappers, and services that overpromise. Zenndra is the straight answer: stable REST endpoints, transparent limits, and infrastructure you can put in front of real users.
Independent · Not affiliated with Medium Corporation
Thousands of apps depended on Medium’s API. When it went away, teams either maintained fragile scrapers or trusted opaque proxies. Neither scales when you have customers counting on you.
Zenndra exposes documented routes for profiles, articles, publications, search, and more — JSON in, JSON out, with rate limits and errors you can explain in a standup.
No stolen credentials, no hidden data harvesting, no surprise bills on the free tier. We publish pricing, ship an OpenAPI spec, and absorb Medium’s front-end churn so your integration doesn’t.
Built by developers who were tired of explaining why the “Medium integration” broke again.
Zenndra started as a reaction to a broken market. After the official API shut down, the space filled with unreliable scrapers and services that hid limits until you were already in production.
We wanted what we always had before: predictable endpoints, typed responses, and documentation that matches reality. So we built it — edge-delivered, versioned routes, a playground to try before you commit, and guides that walk from idea to shipped feature.
We’re not Medium, and we don’t pretend to be. We’re an independent layer that lets you read and work with public Medium data responsibly, with pricing that still makes sense when your side project becomes a product.
Principles we don’t compromise on — because your production app is the proof.
Uptime, consistent response shapes, and incident communication — not “best effort” demos that fall over when traffic spikes.
Reference docs, guides, and OpenAPI stay in sync with what the API actually does. If it’s documented, it behaves that way in staging and prod.
Every tier is hard-capped. When you hit your limit, requests stop — no overage charges, no bill surprises.
Quick facts before you wire us into your stack.
Work with us
Read the docs, try the playground, browse the guides — then create an account for your API key.