Bluesky API for public profile data

One call. Real response.

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

{
  "success": true,
  "platform": "bluesky",
  "endpoint": "bluesky/profile",
  "data": {
    "author": {
      "id": "did:plc:z72i7hdynmk6r22z27h6tvur",
      "handle": "bsky.app",
      "name": "Bluesky",
      "followers": 35065417,
      "following": 15,
      "posts_count": 864,
      "verified": false,
      "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 private accounts. Bluesky has no private profile, so is_private is null.
• No handle-only identity. The anchor is the DID — did:plc: or did:web: — because a handle can be changed and reassigned, and the DID cannot.
• No email or anything behind a login. We read the public AT Protocol record, which is what a logged-out client reads.

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 AT Protocol is public and documented, so this is the cheapest read of the ten — 634 bytes on the wire when measured. What you are handing over is keeping the DID anchor right when a handle moves, and the same field names as the other nine.