Search Mastodon with one API call

Read Mastodon — hashtag timelines and search — without building or maintaining a scraper. Public instance API. Same response shape as every other platform here, so one parser handles all of them. 1 credit a call.

The call

curl -H "x-api-key: $SS_KEY" \
  "https://api.socialsearchapi.com/v1/mastodon/tag?tag=ai"

This call costs 1 credit once you are on credits. A new account gets 5 free calls on any platform — verify an email and this command runs as-is.

What comes back

A real response from this endpoint, captured on 2026-07-25 and trimmed to one item:

{
  "success": true,
  "platform": "mastodon",
  "data": {
    "total": 3,
    "items": [
      {
        "platform": "mastodon",
        "type": "post",
        "text": "Dell 14S review: High-class design and 20+ hour battery lifeThe Dell 14S makes good on its promise of serving as a ch...",
        "url": "https://social.gamefan.net/@techwire/116978987040941635",
        "author": "[email protected]",
        "author_name": "TechWire ⚡",
        "created_at": "2026-07-25T05:34:48Z",
        "metrics": {
          "comments": 0,
          "likes": 0,
          "reposts": 0
        },
        "extra": {
          "created_at_raw": "2026-07-25T05:34:48.000Z"
        }
      }
    ]
  },
  "credits_used": 1
}

Items from Mastodon carry: author, author_name, created_at, extra, metrics, platform, text, type, url.

Why not just scrape it yourself

Mastodon is federated, so there is no single index — what you can see depends on which instance you ask and what it has federated. Full-text search also requires an authenticated token on most instances.

• Cost here: 1 credit a call, $0.003 at list.
• Last verified 2026-07-25: 296ms for this call.
• Coverage: Public posts visible to the instance we query. Federation gaps are inherent.

Other platforms