Medium API for public profile data

One call. Real response.

curl -H "Authorization: Bearer $HH_KEY" \
  "https://honesthook.com/api/v1/medium/profile?handle=markmanson"

{
  "success": true,
  "platform": "medium",
  "endpoint": "medium/profile",
  "data": {
    "author": {
      "id": "db77b01f3f54",
      "handle": "markmanson",
      "name": "Mark Manson",
      "followers": 83742,
      "following": 217,
      "posts_count": null,
      "verified": null,
      "is_private": null
    }
  },
  "error": null,
  "cached": false
}

Recorded response, captured 27 Sep 2026. A live call returns the value at the moment you ask. The same envelope comes back from every other platform — only platform and endpoint change.

What this endpoint does not return.

• No story count. The public profile does not carry a reliable one, so posts_count is null instead of a count of whatever happened to be on the page.
• No verified flag. verifications.isBookAuthor says the person published a book, not that the account is verified, so verified is null.
• No 404 to rely on. A handle that does not exist returns 200 with a not-found page, which is why the read is anchored on the profile object and not on the status code.

A field we cannot read comes back null, never 0. A zero would be a claim about the account; null is a fact about our collection.

The part you are handing over.

The number lives in the Apollo state rather than in the markup, and Medium answers 200 for a handle that does not exist. Keeping the anchor and the state path right when Medium redeploys is the part you are handing over.