Tophhie Cloud API: Two New Endpoints!

We're excited to introduce two new endpoints to the Tophhie Cloud API!

This time, we're gearing them towards our atproto PDS server "Tophhie Social". So, without further ado, let's get into them...

GET - /pds/repos

This API does exactly what it says on the tin. It queries the Tophhie Social PDS server and fetches all repositories currently stored there. You'll also get a count of active, inactive, and total repos.

https://api.tophhie.cloud/pds/repos

As of today (13th Nov 2025), this is what the response looks like.

{
  "total": 18,
  "active": 17,
  "inactive": 1,
  "repos": [
    {
      "did": "did:plc:ggobmtqnjirtchpwgydxoecb",
      "head": "bafyreibhbrhuxainymkfirdfuiskisftq3vqtjrb65cmeyjdh3i2mq6dom",
      "rev": "3m5izt7hobl2p",
      "active": true,
      "status": null
    },
    ...
  ]
}

• A count of total repos.
• A count of active repos.
• A count of inactive repos.
• An array of repository objects.

GET - /pds/blueskyHeatmap

Now, this one takes a little bit longer to run, however it serves a purpose. When you head to https://tophhie.social you'll notice there is a "heatmap" right on the homepage. This heatmap provides a visual overview of the number of Bluesky posts that have been posted to the service, by repos hosted on Tophhie Social.

Previously, the front-end did all the work for this. It queried the repos, then looked inside each repo, counted the posts, organised them by date, and populated the heatmap.

Today, this has changed!

The logic has now been moved to the Tophhie Cloud API. Taking the burden off the front-end and onto our bespoke API service.

https://api.tophhie.cloud/pds/blueskyHeatmap

The response for this one is simple. It's a JSON object, with the property value being a specific date, and the value of that property being the number of posts posted on that day.

{
  "2024-08-02": 1,
  "2024-08-04": 3,
  ...
}

We've made this data publicly available for two reasons:

• To aid in the responsiveness of the Tophhie Social homepage.
• To allow other atproto developers to easily retrieve these statistics for their own display/record purposes.

These are niche APIs, don't get me wrong. However, we hope they serve their purpose and help others 😄

Until next time 👋