Does Medium Have an API in 2026? Auto-Posting, Scheduling, and What Actually Works

Short answer: if you want to auto post to Medium in 2026 using a fresh API integration, you can't. There is no application form to fill out, no developer portal to sign up in, no path from zero to a working key. Medium closed the door and left it closed.

Longer answer: Medium still schedules posts natively, old integration tokens from before the shutdown reportedly still work, and there is a real, if narrower, way to keep Medium in a cross-posting workflow. This is the honest state of it, not the version every three-year-old blog post still repeats.

The API is closed (Medium's own words)

Medium used to run a public API. You'd request a token, hit POST /v1/users/{userId}/posts, and publish straight from your own code. That era is over. Medium's own developer documentation repository now states plainly that the API is no longer supported and that no new integrations are allowed. Not "limited," not "in review." Closed.

This is why every medium api alternative search you run turns up dead links, archived docs, and Stack Overflow answers from 2019 that no longer apply. There's no waitlist to join because there's nothing to wait for. If you're starting from scratch today, the API is off the table, full stop.

That single fact reframes everything else in this guide. You are not choosing between "the easy API way" and "the harder native way." You are choosing between a legacy integration token if you happen to already have one, and Medium's own in-app tools.

What still works: legacy integration tokens

Here's the part that surprises people. If you generated a Medium integration token before the API was shut to newcomers, those tokens reportedly still function. They still authenticate, they can still be used to publish, and they are still revocable from your account settings. What you can't do is create a new one. The generation flow for new tokens is gone.

So if you've got an old medium integration token sitting in an environment variable from some script you wrote years ago, it's worth testing before you assume it's dead. Existing setups appear to have been grandfathered in rather than killed outright. Just treat this as fragile: it's a legacy pathway that Medium hasn't affirmatively killed yet, not a supported product with a roadmap. Don't build a new business process around it. If you have one and it works, use it as a bonus, not a foundation.

If you don't have a token already, this route simply isn't available to you, and no amount of searching will produce one. That's the reality worth accepting early so you stop looking for a signup form that doesn't exist.

Native scheduling: Publish > Schedule for later

The good news is that Medium didn't strip out scheduling when it closed the API. It moved scheduling entirely into the product itself. When you're ready to publish a draft, the Publish flow includes a "Schedule for later" option where you pick a date and time and Medium holds the post until then.

Based on high-confidence secondary reporting, scheduled posts on Medium fire within about five minutes of the time you set. That's not a documented SLA from Medium directly, but it's consistent enough across accounts that it's a reasonable expectation to plan around rather than a hard guarantee to build critical timing on.

This is genuinely how most people schedule posts on Medium now: write the draft, hit Schedule for later, pick the moment, walk away. No token, no API call, no developer account. It's a fine solution for a single article on a single platform. Where it breaks down is coordination: if Medium is one piece of a broader content calendar that also includes your newsletter, your X account, and your LinkedIn page, you're now managing timing in one more disconnected tool.

One number worth debunking while we're here: you'll see claims online of a "10 posts per day" API cap for Medium. There's no current documentation that supports this, and given that the API isn't open to new integrations at all, a rate limit on an API you can't access is close to meaningless. Treat that number as unverified folklore, not a planning constraint.

The import tool + canonical route

If your actual goal is to get content that lives elsewhere onto Medium without hand-copying it, Medium's Import tool is still the intended path. You paste in the URL of a post you've already published on your own blog or another platform, Medium pulls the content in as a draft, and it automatically sets a canonical link back to the original. That canonical tag matters for SEO: it tells search engines the original URL is the authoritative one, so you're not fighting your own content for rankings across two domains.

The workflow this implies is: publish on your own site or blogging platform first, then import into Medium second, letting the canonical URL do the SEO housekeeping. It's manual, but it's also the only route Medium currently endorses for getting external content in, since there's no API to push it programmatically.

Promoting Medium posts on schedule with TimeToPost

Medium isn't a platform TimeToPost posts to directly, and honestly, given that Medium closed the door on new integrations, there's no honest way for any tool to claim a one-click "post to Medium" button right now. What TimeToPost is genuinely good for is the layer around Medium: the calendar that tells you when an article should go live, and the promotion that happens the moment it does.

Here's the pattern that actually works. You write the piece, schedule it inside Medium using Schedule for later, and then use TimeToPost to line up the promotional posts, the X thread, the LinkedIn post, the newsletter mention, so they fire the same day your Medium piece goes live instead of three days later when you remember. You get one calendar view across every platform you actually publish to, with TimeToPost's character counter keeping your promo copy inside each platform's limits and its scheduling queue holding everything until the moment your Medium article clears.

If you're managing more than one or two Medium posts a month alongside any other platform, that coordination is where the real time gets saved, not in the Medium publishing step itself.

FAQ

Is there any way to get new API access to Medium? Not currently. Medium's documentation states the API no longer accepts new integrations, and there's no application process, waitlist, or exception path documented anywhere.

Do old Medium integration tokens expire? There's no fixed expiration Medium documents, and tokens generated before the shutdown reportedly continue to work. They remain revocable from your account settings at any time, by you or by Medium.

Can I edit a Medium post after it's scheduled? Yes, scheduled posts live as drafts until they fire, so you can edit the content, change the scheduled time, or cancel the schedule entirely up until the moment it publishes.

Does cross-posting to Medium hurt my SEO? Not if you use the Import tool's canonical link correctly. Setting your own site as the canonical URL tells search engines which version is authoritative, so publishing on both doesn't create duplicate-content competition against yourself.

Does posting time actually matter on Medium? Less than people assume. Medium's own internal study from 2014 found that publish time was not meaningfully correlated with a post's performance once you controlled for the quality of the writing itself. For the platform-agnostic version of that question across every network you post to, see our best time to post breakdown.

If Medium is one stop on a longer publishing route, the social media scheduler is where the rest of that route gets planned.