Social media data API7 platforms

Seven social networks, one data API

Public account data from X (Twitter), Instagram, TikTok, YouTube, Telegram, Bluesky and LinkedIn over one HTTPS endpoint: follower counts, daily growth history, engagement insights, follower graphs and B2B company records. No app review, no partner programme, no per-platform key.

Get an API keySee every platform

Free forever plan · No credit card required · Cancel anytime

7
Platforms
X, Instagram, TikTok, YouTube, Telegram, Bluesky, LinkedIn
127
Endpoints
Grouped by platform below, every one in the reference
500
Rows per page
Catalogue reads are paged, not one lookup at a time

Pick your platform

Which endpoints exist for each of the seven networks, what a real response looks like, and what does not come back. The endpoint lists are read from the API’s own catalogue, not typed in.

X (Twitter)

68 endpoints built for this platform, 23 more shared by every platform

The official X API prices public reads by tier, and the tier most projects need costs more than the project. This side reads the public profile and its posts: followers, following, post count, verification, account age, daily follower history, measured engagement, top and viral posts, audience overlap and lookalikes, plus a toolbox of follower audits, valuations and shadowban checks.

What you can ask

  • Account check3

    Check one account against our catalog · Check one account live, at the source · Find one handle on every platform at once

  • Catalogue8

    List and filter a catalog · One account or channel · Daily audience history · Inbound graph edges · +4 more

  • Live X content25

    One X profile, live · X's About this account panel · An account's timeline · An account's media timeline · +21 more

  • People search2

    Find one handle across every catalog · Find accounts matching audience and engagement criteria

  • Live fetch2

    Live X profile · Live X profiles, batched

  • Insights9

    Complete intelligence dossier for one X account · Engagement metrics for one X account · The account's permanently kept best posts · What makes this account's posts perform · +5 more

  • Daily movers1

    Biggest audience gains and losses for a day

  • Identity2

    One organisation's accounts across every network, from any one of them · Which company publishes this handle

  • Follower graph4

    Audience overlap between two X accounts · Lookalike X accounts by shared audience · Followers of an X account ranked by their own influence · Follow-graph coverage for one X account

  • Watch and webhooks1

    Watch an account for audience change

  • Tools10

    Value an X account · Check an X account for visibility filtering · Audit an X account's followers for fakes · Measure an X account's engagement rate · +6 more

  • Leads1

    Follower-graph export for one X account

Also on every platform: Account check (2), Catalogue (1), Live fetch (1), Insights (1), Daily movers (1), Identity (2), Watch and webhooks (9), Research findings (4), Tools (2)

Does not return

  • Direct messages, posting, or anything done as a user
  • Protected accounts and their posts
  • Private analytics from X Premium or X Ads

A real response

A follower audit: who is real, who is a bot, and the verdict.

POST/data-api/v2/tools/follower-auditLive call
Body: { "handle": "vercel" }
{
  "data": {
    "profile": {
      "handle": "vercel",
      "followers": 412903,
      "verified": true,
      "account_age_days": 4814
    },
    "composition": {
      "real_percent": 71.4,
      "suspicious_percent": 14.2,
      "bot_percent": 6.8,
      "inactive_percent": 7.6
    },
    "engagement": { "engagement_rate": 0.086, "avg_likes": 214, "avg_views": 41200 },
    "scores": { "quality": 72, "engagement": 48, "account_health": 91 },
    "verdict": "good",
    "sample_size": 200
  },
  "meta": { "request_id": "req_9f2c41a8b3d5", "took_ms": 42, "cache_age_s": 0 }
}
All 68 X (Twitter) endpoints in the reference
Try it

Try it on a real account, right now

No account, no key, no card. Pick a platform and 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

What you can ask, on every platform

Every family below answers the same way whichever network you name: one request shape, one response envelope. The platform tabs above say how deep each one goes there.

Account check

A handle in, an account out: whether it exists, follower count with its precision, verified flag, category, language and how old the reading is. Up to 50 accounts in one POST. Start with GET /accounts/{platform}/{handle}.

Daily growth history

Every catalogued account carries a daily audience series up to 365 days back, with the change per day and a summary of the window. Growth, not a snapshot. GET /directory/{platform}/{id}/growth.

Engagement insights

Measured engagement rates, top posts, posting cadence and the percentile against accounts of the same size, built per platform: X viral patterns, Instagram content mix, Telegram reach, YouTube view velocity. Under /insights.

Follower graph

Who follows whom: inbound and outbound edges on every platform, and on X the audience overlap between two accounts, lookalikes by shared followers and the most influential followers. Under /graph.

Analysis tools

Follower audits, account valuations, shadowban checks, best posting time, engagement calculators and earnings estimates for X, Instagram, TikTok and YouTube. Under /tools, behind their own scope.

Live fetch

When the catalogue is not fresh enough, read the profile at the source and get cache_age_s of zero back. Metered in its own bucket, so paging the catalogue never starves it. GET /accounts/{platform}/{handle}/live.

Live X content

What X is saying right now rather than what the catalogue last saw: advanced post search with X's own operators, an account's timeline, media and mentions, the whole conversation under a post with its quotes and reposters, public list and community timelines, and the real trending board for a place. Under /x, read only.

Watch and webhooks

Register an account and a threshold, and we call your endpoint when its audience moves. Delivery history, failures and replay included. POST /watch.

B2B leads

LinkedIn company records with firmographics, decision makers and role emails, market sizing with real counts, and X follower-graph exports. Under /leads, behind the leads:read scope.

Quickstart

One call, one response envelope

Every endpoint, on every platform, answers with the same two blocks: data and meta. Swap instagram for x, tiktok, youtube, telegram, bluesky or linkedin and the shape does not change. The age of the reading is part of the answer, so you never have to guess how fresh it is.

Request
curl https://pinlyx.com/data-api/v2/accounts/instagram/nasa   -H "Authorization: Bearer psk_live_..."

# or, if your client prefers a plain header:
curl https://pinlyx.com/data-api/v2/accounts/instagram/nasa   -H "x-api-key: psk_live_..."
Response
{
  "data": {
    "platform": "instagram",
    "handle": "nasa",
    "exists": true,
    "evidence": "catalog",
    "identity": {
      "id": "528817151",
      "name": "NASA",
      "url": "https://www.instagram.com/nasa/"
    },
    "audience": { "count": 104443318, "metric": "followers", "precision": "exact" },
    "flags": { "verified": true, "private": false, "nsfw": false },
    "catalog": {
      "state": "present",
      "category": "science",
      "language": "en",
      "data_age_s": 18711,
      "metrics": { "engagement_rate": 0.4213, "avg_likes": 402118 }
    }
  },
  "meta": { "request_id": "req_9f2c41a8b3d5", "took_ms": 42 }
}

Bulk checks take up to 50 accounts per call, directory lookups up to 100 records, and a catalogue page returns up to 500 rows. Metering counts HTTP calls rather than rows, which is where the economics of this API actually live.

What people build with it

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.

Enrich a list of leads

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 checks take 50 accounts a call, so a ten-thousand-row list is two hundred requests rather than ten thousand.

Endpoints

POST /accounts/check · GET /accounts/{platform}/{handle}

Tell a real audience from a bought one

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-audit

Join one person across every network

A 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/graph

Track competitors and clients over time

Store 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}/engagement

Build a B2B company graph

LinkedIn 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}

Give an AI agent real numbers

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/valuation

Against going to each platform directly

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.

CapabilityPinlyx Data APIRecommendedOfficial 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
MinutesDays 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 records in one request
Rarely
Search public posts by keyword, operator and date
X only, with X's own from:, min_faves:, lang: and filter: syntax
Paid tiers
The whole conversation under a post
X only: replies, the thread, quote posts and who reposted it
Paid tiers
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.

What it is, and what it is not

The 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.

It is

  • A read-only HTTP API for public social account data on seven platforms.
  • One key, one bill, one response shape, whichever platform you ask about.
  • A store of daily follower history you did not have to collect yourself.
  • A cross-platform join: one handle resolved against all seven networks at once.
  • Honest about freshness: every catalog answer says how old it is.
  • Bounded in spend: a plan is a monthly budget, and overage is off until you turn it on.

It is not

  • A way to post, send messages or act as a user. Nothing here writes.
  • Access to private accounts, protected posts, stories or direct messages.
  • A replacement for a platform API when the account is yours. Those give you more.
  • A scraper you run. We run the crawlers; you get an HTTP call.
  • A guarantee that a number is live. Catalog reads are cached, and say so.
  • Legal advice. The data is public; what you may do with it is your call to make.

The legal question, answered plainly

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.

One number to think about

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.

Free

$0

100 requests / 30 days

  • Account catalog, all 7 platforms
  • Follower history
  • One key, no card
Start free
Most picked

Starter

$69/ 30 days

20,000 requests / 30 days

  • Live account checks
  • Ownership verification
  • Engagement insights
Choose Starter

Growth

$249/ 30 days

150,000 requests / 30 days

  • Cheaper live calls
  • Higher burst ceiling
  • Ten keys, IP allowlisting
Choose Growth

Scale

$749/ 30 days

750,000 requests / 30 days

  • Every scope, including B2B leads
  • Cheapest live calls
  • Twenty-five keys
Choose Scale
Enterprise. Five million requests, every scope, the highest burst and live-call ceilings, a hundred keys and a number to call. Talk to us.Prices shown are the current published rates and are confirmed at checkout. Overage is off by default; when enabled it is charged at the plan rate up to a cap you set.

Frequently asked questions

X (Twitter), Instagram, TikTok, YouTube, Telegram, Bluesky and LinkedIn. Account checks, daily growth history, identity resolution and watches work the same on all seven. Engagement insights, graph queries and analysis tools are built per platform, and the platform tabs above list exactly which ones exist for each.
For reading public data about accounts you do not own, yes: profile and follower counts, daily follower history, engagement rates, top posts, viral patterns, audience overlap, lookalike accounts, follower audits and valuations, without a developer application or a paid tier. It does not post, read direct messages or act as a user; for that you still need X’s own API.
Yes. X's own advanced search runs through this API with its operators intact, so from:, to:, since:, until:, min_faves:, lang: and filter: all mean what they mean in the X search box, and every result carries its full counter set. Around it: an account's timeline, its media, who mentions it, the direct replies to a post, the whole conversation those replies hang off, the posts that quoted it, the accounts that reposted it, the timeline and members of a public list, a community's posts and moderators, and X's real trending board for a location. Reading only, on public data: nothing here posts, likes, follows or reads a direct message.
Yes. Public profile data (followers, following, posts, bio, category, verified flag) and measured engagement placed against accounts of similar size, for any public account, not only the ones connected to your Facebook Page. Stories, private profiles and insights on accounts you do not own are not available.
Yes. Subscriber counts, daily history, average post views, reach ratio against channels of the same size, audience quality, growth shape and username history, for public channels and groups. The Bot API only exposes any of this for channels you administer.
YouTube: subscribers, lifetime views, video count, daily view velocity ranked against channels of the same size, and ad-revenue and channel-value estimates, without spending Google Cloud quota. TikTok: followers, likes, video counts, growth measured from exact readings, engagement against benchmarks and brand-deal estimates, without a Research API application.
Company records: industry, size band, headquarters, follower trend, staff count, named decision makers, role emails and the company’s other social accounts, filterable by firmographics and enrichable from a website domain. Personal profiles behind a login, connections and employee lists are not available. These endpoints carry their own leads:read scope.
No. There is no Meta App Review, no TikTok sandbox audit, no X developer application and no LinkedIn partner approval. Everything here reads pages a logged-out visitor can see, so an API key is the only credential involved. That also bounds what it can do: nothing that needs a login is available, to us or through us.
Every call that reaches an endpoint and returns a response, including errors you caused. Requests refused before any work happens do not count: unauthenticated calls, scope refusals, and anything rate limited. A live call costs several requests from the budget rather than one, and the multiplier is listed on every plan.
The same account you use for Pinlyx holds the API subscription, and keys are managed in the panel beside everything else. If you are already syncing conversations from Telegram, X or Instagram, this is the data layer that tells you who those people actually are. You do not need to use the CRM to use the API.
By default the API answers 402 and stops, which is the safe behaviour. If you turn overage on, requests past the budget keep being served and are charged to your API credit at your plan rate, up to a cap you set.
Everything returned is collected from public sources. What you may then do with it depends on your jurisdiction and your use case, which is a question for your own counsel. The lead endpoints in particular carry their own scope precisely because they need that thought.
Ready to ship

Start on the free plan

A hundred requests, one key, no card. Enough to check the data is the data you need before any money moves.

Get an API keyTalk to us

Free forever plan · GDPR-ready · No credit card required

Related reading

API reference

Every endpoint with its parameters, scope, limits and error codes, filterable by platform.

All 127 endpoints

The full index, grouped as the API groups them, with a page of its own for every call.

Pricing

Every Pinlyx plan limit side by side, with no per-seat fees.

Contact

Volume pricing, a contract, or a question the docs do not answer.

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.