Coming soonWe are adding Reddit endpoints and more updates.Request an endpoint
Get started for $0
All use cases

Growth dashboards on data that stays consistent.

A snapshot a day for every account you track, IDs that stay the same when someone renames, and a timestamp on every data point.

Get started for $0Read the docs

100 free requests, no card needed.

@nasa · FollowersTracked by ID 528817151 · one snapshot a day
7d30d90d
Followers96,430,911
Last 30 days+412,880
Per day+13,762
Tracked sinceAug 31 rename, same ID
Followers over the last 30 daysRenamed from @nasa_hq · same ID
Aug 3Aug 17Sep 1
Each point is plotted at its capture time, not the fetch time.source cache · freshness 24h

For teams like Beacons, Linktree, Kajabi, Stan, and Fourthwall.

The problem

Why teams use Openhandle.

Basic scraperFollowers · account 528817151 · renamed Sep 1
DayHandleFollowersPoint
Aug 30@nasa_hq96,412,003Plotted
Aug 31@nasa_hq96,430,911Plotted
Sep 1@nasa_hqnot foundLost

The account renamed to @nasa. A scraper keyed on the handle loses the account, and a month of history goes with it.

OpenhandleFollowers · account 528817151 · renamed Sep 1
DayHandleFollowersPoint
Aug 30@nasa_hq96,412,003Plotted
Aug 31@nasa_hq96,430,911Plotted
Sep 1@nasa96,449,819Plotted

Same account, same day. Every response carries the permanent platform ID, so the rename is a label change and the chart keeps going.

Snapshots from cacheA 24-hour cache hit costs $0.0005. A cache miss uses the live price.
IDs survive renamesEvery response carries the permanent platform ID. Track by ID and a rename never breaks a chart.
One documented vocabularyThe metric semantics table says exactly what each metric means per platform and which ones are comparable.
Use the capture timeEach answer shows when we captured it. Use that time to keep late jobs from moving your data points.

How it works

How a tracking job works.

  1. 01

    Track by ID

    Resolve each handle once and store the platform ID. Everything after that is keyed on the ID.

  2. 02

    Snapshot daily from cache

    One 24-hour read per account per day. The response says when the data was captured.

  3. 03

    Plot the capture time

    Store the capture time as the x-axis, not the fetch time. Your time series stores what was true, and when.

Daily snapshot for one account
curl "https://api.openhandle.dev/v1/instagram/profiles/25025320?freshness=24h" \
  -H "Authorization: Bearer $OPENHANDLE_API_KEY"
200 OK
{
  "platform": "instagram",
  "resource": "profile",
  "capturedAt": "2026-09-01T22:40:11Z",
  "source": "cache",
  "data": {
    "id": "25025320",
    "handle": "instagram",
    "metrics": {
      "followers": 690412330,
      "following": 118,
      "posts": 8104
    }
  }
}

Served from cache. The capture time is the truth for your time series, not the moment you fetched it.

Trust

Keep your reporting data consistent.

Proper invoicing

Card payment, an invoice for every charge. Nothing prepaid, nothing that expires.

A person answers

Chat directly with the people who build Openhandle through Crisp.

Documentation

Read how it works.

Freshness and caching

Read the docs

Metric semantics

Read the docs

Identifiers

Read the docs

Send your agent ahead.

Paste the prompt into your agent and it sets everything up. Or come yourself, it takes five minutes.

For agents
Get started for $0Read the quickstart