Mastodon API for public profile data

One call. Real response.

curl -H "Authorization: Bearer $HH_KEY" \
  "https://honesthook.com/api/v1/mastodon/profile?handle=Gargron@mastodon.social"

{
  "success": true,
  "platform": "mastodon",
  "endpoint": "mastodon/profile",
  "data": {
    "author": {
      "id": "https://mastodon.social/users/Gargron",
      "handle": "Gargron@mastodon.social",
      "name": "Eugen Rochko",
      "followers": 382854,
      "following": 743,
      "posts_count": 82332,
      "verified": null,
      "is_private": false
    }
  },
  "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 handle without an instance. On a federated network @name alone identifies nobody, so a handle with no instance is refused with 400 instead of guessed.
• No numeric id. The id is the ActivityPub uri, because the numeric id is local to one server — the same account has a different one on every instance.
• No verified flag. Mastodon verifies links, not identity, so verified is null rather than reporting a link check as an identity check.

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 request goes to the account's origin instance, which is the authoritative one, and every instance runs its own version of the software. Keeping that working across thousands of servers is the part you are handing over.