Tutorials
GitHub profile in curl
One authenticated call to /api/v1/github/profile?handle=torvalds, the response it returned, and the line that reads one field out of it.
What you need
curl ships with macOS and most Linux distributions, and with Windows 10 and later. There is nothing to install.
The call
curl -H "Authorization: Bearer $HH_KEY" \
"https://honesthook.com/api/v1/github/profile?handle=torvalds"
What came back
{
"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, not this one.
Every field in that capture
| In curl | Type in this capture |
|---|
.success | boolean |
.platform | string |
.endpoint | string |
.data.author.id | string |
.data.author.handle | string |
.data.author.name | string |
.data.author.followers | number |
.data.author.following | number |
.data.author.posts_count | null |
.data.author.verified | null |
.data.author.is_private | null |
.error | null |
.cached | boolean |
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 full list of what this route does not return is on github-api/profile.
Reading one field
curl -H "Authorization: Bearer $HH_KEY" \
"https://honesthook.com/api/v1/github/profile?handle=torvalds" \
| jq -r '.data.author.followers'
jq is a separate tool — it is not part of curl. Without it the command above prints the whole envelope, which is the block below.
GitHub is the easy one. It runs an official public API, it needs no token for a public user, and the shape it returns is stable. So the honest question about this endpoint is what you are getting that you could not get by calling api.github.com yourself.
The answer is the normalisation, and it is narrower than a sales page would claim.
What you are calling
You are calling our endpoint, with your key in an Authorization header. Behind it, GitHub's official API. What comes back is the same eight-field envelope that Instagram, TikTok, Bluesky and every other profile route here return — Hacker News is the exception, because it answers a search, and its author block carries three fields rather than eight. So a client you write once reads all of them, and adding a platform does not mean adding a parser.
Where GitHub has nothing to give, the field is null instead of being filled from a neighbouring number that means something else. That decision is the product here.
Before you copy the block
Keep the key in an environment variable — all three examples read HH_KEY.
If GitHub is the only platform you need, call GitHub directly; that is a real answer and this page is not going to pretend otherwise. The envelope earns its keep at the second platform.