Resolve a handle to a real account across X, Instagram, TikTok, YouTube, Telegram, Bluesky and LinkedIn. Follower history, engagement, bulk enrichment and cross-platform identity, from crawlers we run ourselves. No app review, no platform approval, no per-platform key.
Free forever plan · No credit card required · Cancel anytime
No account, no key, no card. Pick a call, type a handle, and read exactly what your own integration would get back.
Five calls a day from this address. A free account gets its own key and its own budget. Get your own key
Six things the official APIs will not give you without approval, a partner agreement, or both.
Resolve a handle to a real account: follower count, bio, category, language and country. Bulk endpoints answer up to 100 identifiers in a single request, so a whole list costs a handful of calls rather than one per row.
One handle in, every account that belongs to the same person or company out. Resolve across all seven networks in a single request, or ask which company publishes a handle. The join you would otherwise be doing by hand in a spreadsheet.
Every catalogued account carries daily follower history, so you can ask what moved this week instead of what the number is today. Useful the moment you need to tell a real audience from a bought one.
Most questions are answered from our own database in one request. When a stored value is not fresh enough, the live endpoints go to the platform at request time and report an age of zero, so freshness is a decision you make per call.
Catalog responses carry cache_age_s in their meta block. You never have to assume how old a number is, and you can decide in code whether it is recent enough for what you are doing.
A plan is a monthly request budget. Past it the API stops with a 402 by default; turn overage on and it keeps serving up to a cap you set. A runaway job cannot spend money you did not plan to spend.
The same request shape and the same response envelope on all seven. What differs is what each platform makes public, and each card says so.
Handle to account: followers, following, post count, bio, verification, account age and daily follower history. The alternative people reach for when the official X API tier they need costs more than the project.
Public profile data without Meta App Review, a business verification call or a connected Facebook Page. Useful the moment you need creator data for accounts that are not yours.
Creator lookups without a sandbox audit or a Research API application. Follower counts and engagement on public creator accounts.
Channel data that does not spend your Google Cloud quota. The official Data API is free until 10,000 quota units a day, and a list call costs more than most people expect.
Public channel and group statistics, which the Bot API does not expose for channels you are not an administrator of.
AT Protocol accounts alongside the rest, so a cross-platform lookup does not need a second client and a second set of types.
Company pages without the LinkedIn Partner Program. This is the platform whose official API is hardest to reach, and the one where the gap matters most for B2B.
Every endpoint answers with the same two blocks: data and meta. The age of the number is part of the answer, so you never have to guess how fresh it is.
curl https://crmsolid.com/data-api/v2/accounts/x/nasa \
-H "Authorization: Bearer psk_live_..."
# or, if your client prefers a plain header:
curl https://crmsolid.com/data-api/v2/accounts/x/nasa \
-H "x-api-key: psk_live_..."{
"data": {
"platform": "x",
"handle": "nasa",
"display_name": "NASA",
"followers": 96412338,
"verified": true,
"category": "science",
"country": "US",
"language": "en",
"growth": { "d7": 18422, "d30": 71903 }
},
"meta": { "cache_age_s": 3120, "cost": 1 }
}Bulk endpoints take up to 100 identifiers per call, and a catalog page returns up to 500 rows. Metering counts HTTP calls rather than rows, which is where the economics of this API actually live.
Not a replacement for the official APIs. A different job: reading public data about accounts you do not own, on seven platforms, without seven integrations.
| Capability | CRM Solid Data APIRecommended | Official platform APIs |
|---|---|---|
| Getting started | ||
Approval before you can read public data App review, partner programmes, sandbox audits | None | Usually required |
One key for all seven platforms | One per platform | |
One bill | Seven relationships | |
Time from signup to first response | Minutes | Days to weeks |
| What you can read | ||
Public account data on accounts you do not own | Varies by platform | |
Daily follower history you did not have to collect Growth over the last 7, 30 or 90 days | Snapshot only | |
The same field names across every platform | Seven shapes | |
Up to 100 accounts in one request | Rarely | |
Private insights on accounts you own | ||
Posting, direct messages, acting as a user | ||
| Operating it | ||
How old the data is, on every response cache_age_s in the meta block | ||
Force a fresh read at request time | Live endpoints | |
A spending cap you set | Tier ceilings | |
Breaking changes when a platform changes its API | We absorb them | Yours to fix |
The official APIs are the right tool for anything about an account you own or a user who has authorised you: posting, direct messages, private insights. What they make hard is the other case, which is what this exists for. Vendor terms and pricing change; check theirs before you choose.
Six jobs that need public data about accounts somebody else owns. The endpoints that do each one are named, so you can price the work before you write it.
You have handles and nothing else. Turn each one into a real account with a follower count, a bio, a category, a language and a country, then decide who is worth a message. Bulk endpoints take 100 identifiers a call, so a ten-thousand-row list is a hundred requests rather than ten thousand.
Endpoints
POST /accounts/check · GET /accounts/{platform}/{handle}A follower count on its own says nothing. Daily history says whether it arrived steadily or in a single afternoon, and the follower audit puts a number on how much of it looks inorganic. This is the check that stops an influencer budget going to a bot farm.
Endpoints
GET /accounts/{platform}/{handle}/history · GET /tools/follower-auditA handle on one platform is half an identity. Resolve it against all seven at once, or ask which company publishes it, and the row in your CRM stops being a Twitter handle and starts being a person with a company, a country and five other accounts.
Endpoints
GET /accounts/resolve · GET /identity/resolve · GET /identity/graphStore the daily numbers you would otherwise have to collect yourself. Movers tell you who changed most today; history tells you whether last month was a trend or one good post.
Endpoints
GET /directory/{platform}/movers · GET /insights/{platform}/{handle}/engagementLinkedIn company pages without the Partner Program: followers, employee band, industry, headquarters. The lead scopes carry their own permission precisely because this is the data that needs a second thought about how you use it.
Endpoints
GET /leads/companies · GET /leads/companies/{id}A model asked "is this creator worth working with" will invent an answer unless something hands it one. One HTTP call per account, a stable envelope, and a cache age on every field so the agent can say how fresh its evidence is.
Endpoints
GET /accounts/{platform}/{handle} · GET /tools/valuationThe boundaries are the product. Everything here reads pages a logged-out visitor can see, and that single fact decides both what it can do and what it cannot.
Everything returned is collected from sources a logged-out visitor can reach. That is why there is no app review to pass and no partner agreement to sign. It is also the limit: nothing behind a login is available, to us or through us. What you may then do with public data depends on where you are and what you are doing, and the lead endpoints in particular carry their own scope because they need that thought. If your use case touches personal data of people in the EU, UK or California, treat this the way you would any other data source and ask your own counsel.
How many requests a month. Every plan reads the same catalog across the same seven platforms; they differ in volume, in burst ceiling, and in which scopes they unlock.
100 requests / 30 days
20,000 requests / 30 days
150,000 requests / 30 days
750,000 requests / 30 days
A hundred requests, one key, no card. Enough to check the data is the data you need before any money moves.
Free forever plan · GDPR-ready · No credit card required
We value your privacy
We use cookies to improve our site, analyze traffic, and personalize ads. You can accept all, reject non-essential, or customize your choices. Read our Cookie Policy.