Medium scraper API
The InsightSocial Medium API has 6 endpoints, from 20 credits a call. A tag posts call costs 20 credits, about $0.02 on Pro, and your first 10 calls up to 100 credits each are free.
The Medium scraper API for the newest posts of an author, a publication or a tag, with the full article HTML where Medium serves it, and daily sitemaps of every post URL.
6 endpoints · from 20 credits a call · 10 free calls up to 100 credits each · no credit card
curl "https://api.insightsocial.app/v1/medium/tag/posts?tag=javascript" \-H "x-api-key: $INSIGHTSOCIAL_API_KEY"
What Medium data can you get?
Public Medium data only, in the same JSON envelope as every other platform. Every Medium endpoint is beta: inside data it returns Medium's own structure under our naming rules (snake_case keys, string ids, ISO times where Medium gives a timestamp), not the shared profile and post schema, and fields may change.
Authors and publications
An author's ten newest posts, with the full article HTML when it is available, and a publication's ten newest, by slug or its own domain, optionally by tag.
What people build with the Medium API
Content monitoring
Check the authors and publications in your space on a schedule and catch new posts the day they appear.
Topic research
Read the newest posts under a tag to see what writers are covering, with snippets and images to sort by.
Archives and datasets
Walk a day's sitemap for every post URL and its last-modified date, then fetch the authors you care about.
Medium API endpoints
All 6 Medium endpoints and their price in credits. Every one has a fixed price.
| Endpoint | Credits | What it returns |
|---|---|---|
| /author/posts | 20 | List an author's ten newest Medium posts, with the full article HTML when the article body is available. |
| /discover | 20 | List the user, publication, tag, list, topic, removed-post or removed-user URLs in one day's Medium sitemap. |
| /posts | 20 | List the post URLs and last-modified dates in one UTC day's Medium sitemap, paged with a cursor. |
| /publication/posts | 20 | List a publication's ten newest Medium posts by Medium slug or its own domain, optionally filtered by tag. |
| /sitemap | 40 | List one page of the available Medium sitemap files of one kind, with the newest real file. |
| /tag/posts | 20 | List the ten newest Medium posts carrying a tag, with snippets and first image when available. |
Parameters, response fields and examples for each endpoint are in the Medium API reference.
InsightSocial vs the official Medium API
Medium's documented API publishes posts to the authenticated user's own account. It has no endpoints for reading other authors' posts.
| InsightSocial API | Official Medium API | |
|---|---|---|
| Reading posts | Author, publication and tag posts | Not documented |
| Publishing | Not offered | Posts to your own account |
| Setup | Sign in and copy a key | An integration token for your account |
| Cost per call | 20 credits | No per-call price; publishing only |
The official API is the right tool for posting, messaging or managing accounts you own. This one is read-only public data.
How much does the Medium API cost?
Medium calls start at 20 credits. Every endpoint's price is in the table above and in the free GET /v1/endpoints catalogue, so you know the cost before you call. Pro's 10,000 monthly credits cover about 500 tag or author reads at 20 credits each.
Failed calls are free
A call that errors or finds nothing costs 0 credits.
Repeats and retries
A repeat call is charged again: the full price when it fetches new data, 2 credits when the answer comes from the shared cache. Add fresh=1 to force a new read. Only a retry with the same Idempotency-Key is free.
One balance
API calls and Chrome extension exports share the same credits. The free plan includes 500 a month.
Not writing code?
Connect InsightSocial to Claude or ChatGPT and ask for Medium data in plain English. Same account, same credits.
Medium API: frequently asked questions
Medium's documented API is for publishing to your own account; it has no endpoints for reading other people's posts. /v1/medium/author/posts, /v1/medium/publication/posts and /v1/medium/tag/posts read public posts with one key.
/v1/medium/author/posts includes the full article HTML when Medium serves the body, and says when it does not. Tag lists carry a snippet and the first image.
Author, publication and tag lists return the ten newest posts. For history, /v1/medium/posts lists every post URL in one UTC day's sitemap, with a cursor.
They return Medium's own record shapes under our naming rules (snake_case keys, string ids and ISO times) rather than the shared post entity, so fields may change. Every Medium endpoint is 20 credits a call except the sitemap file list, which is 40. Calls that fail or find nothing are free.
No. There is no Medium app, OAuth flow or review. One API key in the x-api-key header works for Medium and the other 60 platforms.
Yes. Your first 10 calls priced at 100 credits or less are free, and the free plan includes 500 credits every month. No credit card is needed to get a key.
60 requests a minute and 10 requests in flight at once, per API key. Going over either returns a 429 with a Retry-After header, and a rejected request costs nothing. There is no daily quota: past those two limits, your credit balance is what bounds volume.
List endpoints return rows in data.items and a pagination object with next_cursor and has_more. Send next_cursor back unchanged as the cursor parameter for the next page, and stop when has_more is false. A handful of endpoints page with their own parameter instead; their reference pages name it.
No. A call that errors or finds nothing costs 0 credits. A live fetch costs the endpoint's price, or for a metered endpoint what it actually read. A repeat call is charged again: the full price when it fetches new data, 2 credits when the answer comes from the shared cache. Add fresh=1 to force a new read. Only a retry with the same Idempotency-Key is free.
A call fetches live unless a recent copy is in the shared cache, and every response says which with the cached field; a cached answer costs 2 credits. Add fresh=1 or send Cache-Control: no-cache to skip the cache; that call is charged at the normal price.
Collecting publicly available data is generally treated differently from accessing private data, but the answer depends on your jurisdiction, Medium's terms and what you do with personal data afterwards. The API reads public data only. Talk to a lawyer for anything commercial.
Medium API guides
The same key works for 60 more platforms
- TikTok scraper API
- LinkedIn scraper API
- Twitter/X scraper API
- YouTube scraper API
- Reddit scraper API
- Pinterest scraper API
- Bluesky scraper API
- Truth Social scraper API
- Snapchat scraper API
- Telegram scraper API
- Twitch scraper API
- Kick scraper API
- Rumble scraper API
- Kwai scraper API
- Douyin scraper API
- Xiaohongshu (RedNote) scraper API
- Quora scraper API
- TikTok Shop scraper API
- Weibo scraper API
- Zhihu scraper API
- Substack scraper API
- Nextdoor scraper API
- Amazon scraper API
- App Store scraper API
- Apple Music scraper API
- Behance scraper API
- Dailymotion scraper API
- Deezer scraper API
- DEV Community scraper API
- Discord scraper API
- Dribbble scraper API
- Fandom scraper API
- Flickr scraper API
- GitHub scraper API
- Google Ads Transparency scraper API
- Google News scraper API
- Google Trends scraper API
- Gumroad scraper API
- Hacker News scraper API
- Hugging Face scraper API
- Ko-fi scraper API
- Lemmy scraper API
- Letterboxd scraper API
- Linktree scraper API
- Lnk.Bio scraper API
- Mastodon scraper API
- MyAnimeList scraper API
- npm scraper API
- Polymarket scraper API
- Product Hunt scraper API
- Shopify scraper API
- SoundCloud scraper API
- Spotify scraper API
- Stack Overflow scraper API
- Stan Store scraper API
- Steam scraper API
- Vimeo scraper API
- Wikipedia scraper API
- Yahoo Finance scraper API
- Yelp scraper API