Pinterest API for public profile data

One call. Real response.

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

{
  "success": true,
  "platform": "pinterest",
  "endpoint": "pinterest/profile",
  "data": {
    "author": {
      "id": "pinterest",
      "handle": "pinterest",
      "name": "Pinterest",
      "followers": 6264894,
      "following": null,
      "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 following and no pin count. The public profile page does not carry them, so both stay null instead of being filled from a neighbouring counter.
• No verified flag. Pinterest has three different badges — domain verified, verified merchant, verified identity — and picking one would publish a badge the platform did not give.
• No board counters. The name follower_count appears 42 times on the page; on the profile measured when this route was built, the profile counter read 556,445 while two board counters on the same page read 527,020 and 526,128.

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.

This is read from the ld+json ProfilePage block, not with a regular expression, because the page carries dozens of counters with the same name. Keeping that block parsed when Pinterest moves it is the part you are handing over.