GitHub API for public profile data

One call. Real response.

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

{
  "success": true,
  "platform": "github",
  "endpoint": "github/profile",
  "data": {
    "author": {
      "id": "1024025",
      "handle": "torvalds",
      "name": "Linus Torvalds",
      "followers": 325402,
      "following": 0,
      "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 post count. public_repos counts repositories, not posts, so posts_count stays null instead of borrowing a number that means something else.
• No verified flag. GitHub has no verification badge for user accounts, so verified is null rather than false — absent is not negative.
• No private accounts. A GitHub user page is public or it does not exist, so is_private is null for the same reason.

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.

GitHub serves this from its official API, so the shape is stable and the read needs no browser. What you are handing over is the normalisation: the same eight fields as every other network, with the three GitHub does not have marked null instead of guessed.