Universal Search Multi API
Scrape Universal Search Multi data with one API call. Runs the same query on several platforms' native search endpoints at once and returns their rows together: TikTok (`/v1/tiktok/search`), Instagram reels (`/v1/instagram/search/reels`), YouTube (`/v1/youtube/search`), Reddit (`/v1/reddit/search`), Threads (`/v1/threads/search`), X (`/v1/twitter/search/tweets`), Facebook (`/v1/facebook/search/posts`) and LinkedIn (`/v1/linkedin/search/posts`). `platforms` picks them (default tiktok,instagram,youtube,reddit,threads). Every row in `data.items` is exactly the row that platform's own endpoint returns, with its `post` and `computed` blocks, plus `platform`. Rows are grouped by platform in the order you asked for them, in each platform's own order, and a post URL that already appeared is dropped (`data.duplicates_removed`). Each platform's own filters pass through with a platform prefix, for example `tiktok.region=US` or `reddit.sort=new`. `since` keeps only posts published on or after a date on every platform; a row without a date is kept. It is sent to the platform as a native filter where one exists (Threads and Facebook `start_date`, the X `since:` operator). `data.sources` reports each platform: `status` (`ok`, `empty` or `failed`), the rows it returned and kept, the credits it cost, and its `next_cursor`, which you send as `cursor` to that platform's own endpoint (listed in `endpoint`) for its next page. This endpoint does not page itself. For a planned, reranked and clustered answer across more sources, use /v1/search/everywhere.
Last updated September 2026Maintained by the SocialCrawl team
Returns each chosen platform's own search results for one query in one list, tagged by platform and deduped by URL, with each platform's own endpoint for going further.
Use it instead of calling several platforms' search endpoints yourself; for a ranked, summarised answer use search/everywhere.
Searching 67 platforms in parallel
What can you do with the Multi API?
The Multi endpoint gives you structured Universal Search data with computed fields in a single request. No scraping infrastructure to build or maintain.
Example Request
curl -H "x-api-key: YOUR_API_KEY" \
"https://www.socialcrawl.dev/v1/search/multi?query=matcha+latte&platforms=tiktok%2Cinstagram%2Cyoutube&since=2026-09-01&tiktok.region=US"import requests
response = requests.get(
"https://www.socialcrawl.dev/v1/search/multi",
params={
'query': 'matcha latte',
'platforms': 'tiktok,instagram,youtube',
'since': '2026-09-01',
'tiktok.region': 'US',
},
headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()const response = await fetch(
"https://www.socialcrawl.dev/v1/search/multi?query=matcha+latte&platforms=tiktok%2Cinstagram%2Cyoutube&since=2026-09-01&tiktok.region=US",
{
headers: { "x-api-key": "YOUR_API_KEY" },
},
);
const data = await response.json();Parameters
| Parameter | Required | Description |
|---|---|---|
| query | Yes | Keyword or phrase, sent unchanged to every platform (1-500 characters). |
| platforms | No | Comma-separated platforms to search: tiktok, instagram, youtube, reddit, threads, twitter, facebook, linkedin. Default tiktok,instagram,youtube,reddit,threads. Each one costs its own endpoint's page price, and only when its page came back with rows. |
| since | No | Keep only posts published on or after this date on every platform: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. A row with no date is kept. A platform page trimmed to nothing still costs its page, as it would on that platform's own endpoint. |
| tiktok.date_posted | No | TikTok only. Sent to /v1/tiktok/search as `date_posted`, exactly as that endpoint takes it. One of: yesterday, this-week, this-month, last-3-months, last-6-months, all-time. (yesterday | this-week | this-month | last-3-months | last-6-months | all-time) |
| tiktok.sort_by | No | TikTok only. Sent to /v1/tiktok/search as `sort_by`, exactly as that endpoint takes it. One of: relevance, most-liked, date-posted. (relevance | most-liked | date-posted) |
| tiktok.region | No | TikTok only. Sent to /v1/tiktok/search as `region`, exactly as that endpoint takes it. |
| instagram.date_posted | No | Instagram only. Sent to /v1/instagram/search/reels as `date_posted`, exactly as that endpoint takes it. One of: last-week, last-month, last-year. (last-week | last-month | last-year) |
| youtube.uploadDate | No | YouTube only. Sent to /v1/youtube/search as `uploadDate`, exactly as that endpoint takes it. One of: today, this_week, this_month, this_year. (today | this_week | this_month | this_year) |
| youtube.sortBy | No | YouTube only. Sent to /v1/youtube/search as `sortBy`, exactly as that endpoint takes it. One of: relevance, popular. (relevance | popular) |
| youtube.type | No | YouTube only. Sent to /v1/youtube/search as `type`, exactly as that endpoint takes it. One of: videos, shorts. (videos | shorts) |
| youtube.duration | No | YouTube only. Sent to /v1/youtube/search as `duration`, exactly as that endpoint takes it. One of: under_3_min, between_3_and_20_min, over_20_min. (under_3_min | between_3_and_20_min | over_20_min) |
| youtube.region | No | YouTube only. Sent to /v1/youtube/search as `region`, exactly as that endpoint takes it. |
| reddit.sort | No | Reddit only. Sent to /v1/reddit/search as `sort`, exactly as that endpoint takes it. One of: relevance, new, top, comment_count. (relevance | new | top | comment_count) |
| reddit.timeframe | No | Reddit only. Sent to /v1/reddit/search as `timeframe`, exactly as that endpoint takes it. One of: all, day, week, month, year. (all | day | week | month | year) |
| threads.start_date | No | Threads only. Sent to /v1/threads/search as `start_date`, exactly as that endpoint takes it. |
| threads.end_date | No | Threads only. Sent to /v1/threads/search as `end_date`, exactly as that endpoint takes it. |
| twitter.sort | No | X only. Sent to /v1/twitter/search/tweets as `sort`, exactly as that endpoint takes it. One of: latest, top. (latest | top) |
| facebook.start_date | No | Facebook only. Sent to /v1/facebook/search/posts as `start_date`, exactly as that endpoint takes it. |
| facebook.end_date | No | Facebook only. Sent to /v1/facebook/search/posts as `end_date`, exactly as that endpoint takes it. |
| facebook.recent_posts | No | Facebook only. Sent to /v1/facebook/search/posts as `recent_posts`, exactly as that endpoint takes it. |
| facebook.location_uid | No | Facebook only. Sent to /v1/facebook/search/posts as `location_uid`, exactly as that endpoint takes it. |
| linkedin.sort_by | No | LinkedIn only. Sent to /v1/linkedin/search/posts as `sort_by`, exactly as that endpoint takes it. One of: date_posted, relevance. (date_posted | relevance) |
| linkedin.date_posted | No | LinkedIn only. Sent to /v1/linkedin/search/posts as `date_posted`, exactly as that endpoint takes it. One of: past_24h, past_week, past_month. (past_24h | past_week | past_month) |
| linkedin.content_type | No | LinkedIn only. Sent to /v1/linkedin/search/posts as `content_type`, exactly as that endpoint takes it. One of: videos, photos, jobs, live_videos, documents, collaborative_articles. (videos | photos | jobs | live_videos | documents | collaborative_articles) |
| relevance | No | Optional. Without this param every row already carries computed.relevance against your query, free ({ p, sense, depth, spam }: is this row about what your query means, or a different thing that shares its words?), and nothing is dropped or reordered. score asks for it explicitly and waits for every row; filter also drops the rows that are not about your query, and lists their ids in data.relevance.dropped_ids. Your query is the topic; nothing to configure. A row that could not be judged is never dropped and carries relevance: null. Pagination is unchanged, so a filtered page can hold fewer rows. Free with your query as the topic; with relevant_to it adds 1 credit per started 25 newly judged rows (rows already judged for the same topic are free, and so is a cached page). (score | filter) |
| relevance_threshold | No | Optional, only with relevance. The probability (0 to 1) a row must reach to be kept by relevance=filter. Default 0.5. Lower keeps more rows, higher keeps fewer. |
| relevant_to | No | Optional, only with relevance. Up to 200 characters describing what you mean, used as the topic instead of the query. Use it when the query is ambiguous, for example query=cleopatra with relevant_to=Cleopatra, the IGT slot game. |
| judgments | No | Optional, on (the default) or off. By default every row gains free SocialCrawl judgments (computed.labels, and computed.relevance on search endpoints), reported in data.labels (mode default) and data.relevance (origin default), each with a status (complete, partial or skipped) and pending: the rows still being judged when the page was sent, which carry null now and are filled on your next call or cached read. Default judgments never add credits, never change an existing field, and never drop or reorder a row. off returns the page exactly as before, with none of those keys. label=none does the same. (on | off) |
| dry_run | No | Optional. When 1, return a cost preview for this labelled or relevance-filtered request without fetching the page or judging any row. data.estimate reports rows_expected, rows_cached, label_credits_min, label_credits_max and base_credits. 0 credits charged. (1) |
| fit | No | Optional. When goal, keep the rows and fields needed for the goal you pass in goal= (plus any that are uncertain, and the first and last), and replace the rest with a stub. data.held_back lists the held ids and a recall id that re-reads the full page from cache at no extra charge. Without this param the page is unchanged. (goal) |
| goal | No | Required by fit=goal. What you are trying to do, in your own words, up to 300 characters. |
| fit_tokens | No | Optional, only with fit=goal. Soft cap on how much of the page to keep, in tokens. Uncertain blocks and the first and last block are kept even if they exceed it. |
| label | No | Optional CSV of SocialCrawl labels to add to every post. Without this param every page already carries sponsored, intent and niche, free; label= adds the labels you name to them (the defaults keep running). sponsored, intent and niche are free when asked for too; mention, quality, intent with offer=, and injection add 1 credit per started 25 newly judged posts. judgments=off (or label=none) turns the default labels off. sponsored: is the post a paid or gifted promotion (p, 0 to 1), did it carry a disclosure marker such as #ad or 광고 (disclosed), is it likely paid with no marker (undisclosed), and which of the accounts it mentions does it promote (brand, or null). These are signals to review, never a finding. mention (needs brand=): is the post about that brand rather than something that shares its name (about_brand, 0 to 1), how it feels about the brand on five levels (sentiment_level 0 to 4 and sentiment_score 0 to 1, null when the post is not about the brand), is it sarcastic, which aspect it talks about (taste_or_quality, price_or_value, availability_or_delivery, health_or_safety, advertising_or_campaign, customer_service, none), and did the author buy or use it (first_hand). intent: what the author is mainly doing (label: asking_for_recommendation, comparing_options, switching_away, complaining, promoting, news_or_discussion, other, or null when unsure, with confidence), whether they read as a potential buyer rather than a seller (buyer, seller), how pressing the need is (urgency, 0 to 3), and, when you pass offer=, whether your offer would plausibly help them (fits_offer). niche: which of the 33 niches of the published taxonomy sc-niche-v1 the caption belongs to, or personal_no_niche, or other (label, confidence, taxonomy), with label null when the caption is too thin to tell or the pick is unsure. It reads the caption only, not the video. quality: how much checkable detail the caption carries (fact_density 0 to 3), whether it mainly asks for likes, replies, shares, follows or tags (engagement_bait, 0 to 1), whether it is written to provoke anger as a way to get engagement (rage_bait, 0 to 1; about the writing, never the side taken), whether it only repeats someone else's news or view (secondhand, 0 to 1), and what the post is mainly doing (post_aim: inform, opinion, sell, entertain, provoke, other). exclude=engagement_bait drops posts whose engagement_bait is 0.8 or higher. injection flags text that addresses an AI system and tries to direct it (flagged, p); it never drops or rewrites a row. A post that could not be judged carries labels: null. Posts already labelled for anyone are free, and so is a cached page. data.labels reports what was judged and billed. |
| exclude | No | Optional CSV (engagement_bait), only with label=quality. Drops posts whose engagement_bait probability is 0.8 or higher and lists their ids in data.labels.dropped_ids. A post that could not be judged is never dropped. |
| brand | No | Required by label=mention, ignored otherwise. The brand or product the posts are judged against, up to 300 characters, for example brand=Buldak. Without it label=mention is skipped with the warning label_mention_needs_brand and is not billed. |
| brand_description | No | Optional, with label=mention. One plain sentence saying what the brand is, for example brand_description=Samyang's spicy instant noodle brand. Use it when the name is also an ordinary word or another company's name. |
| offer | No | Optional, with label=intent. One or two plain sentences saying what you sell, up to 300 characters, for example offer=A web design agency that builds websites for small businesses. Adds fits_offer to every post; without it fits_offer is null. |
| label_evidence | No | Optional, only with label=. When 1, every labelled row also carries computed.labels_evidence.<preset> = { quote, sentence_index }: the sentence in the row that most clearly shows the label, copied verbatim. Absent or null when no single sentence shows it. (1) |
What does the Universal Search Multi API return?
Every response follows one unified schema. Here is a real, unmodified response body, so you can see the exact fields you get back before spending a credit.
Example response
{
"success": true,
"platform": "instagram",
"endpoint": "/v1/instagram/engagement",
"data": {
"engagement_rate_percentages": 38.33,
"recent_posts": 12,
"followers": 87608035,
"comments": 528912,
"likes": 33049046,
"recent_posts_explanation": "Statistics based on the last 12 posts",
"id_user": "2278169415",
"username": "mrbeast",
"is_private": false,
"posts_details": [
{
"likes": 5636982,
"comments": 69484,
"taken_at": 1781457954,
"datetime": "2026-06-14 20:25:54",
"hours_since_post": 461,
"time_ago": "19 days ago",
"likes_per_hour": 12228,
"comments_per_hour": 151
},
{
"likes": 20000768,
"comments": 223510,
"taken_at": 1732824650,
"datetime": "2024-11-28 23:10:50",
"hours_since_post": 13971,
"time_ago": "2 years ago",
"likes_per_hour": 1432,
"comments_per_hour": 16
},
{
"likes": 929226,
"comments": 30633,
"taken_at": 1782232475,
"datetime": "2026-06-23 19:34:35",
"hours_since_post": 246,
"time_ago": "10 days ago",
"likes_per_hour": 3777,
"comments_per_hour": 125
},
{
"likes": 487761,
"comments": 22482,
"taken_at": 1781799425,
"datetime": "2026-06-18 19:17:05",
"hours_since_post": 366,
"time_ago": "15 days ago",
"likes_per_hour": 1333,
"comments_per_hour": 61
},
{
"likes": 712265,
"comments": 15716,
"taken_at": 1781366405,
"datetime": "2026-06-13 19:00:05",
"hours_since_post": 487,
"time_ago": "20 days ago",
"likes_per_hour": 1463,
"comments_per_hour": 32
},
{
"likes": 1475116,
"comments": 35386,
"taken_at": 1781277094,
"datetime": "2026-06-12 18:11:34",
"hours_since_post": 512,
"time_ago": "21 days ago",
"likes_per_hour": 2881,
"comments_per_hour": 69
},
{
"likes": 1108220,
"comments": 26632,
"taken_at": 1780160249,
"datetime": "2026-05-30 19:57:29",
"hours_since_post": 822,
"time_ago": "1 months ago",
"likes_per_hour": 1348,
"comments_per_hour": 32
},
{
"likes": 542948,
"comments": 28476,
"taken_at": 1779375582,
"datetime": "2026-05-21 17:59:42",
"hours_since_post": 1040,
"time_ago": "1 months ago",
"likes_per_hour": 522,
"comments_per_hour": 27
},
{
"likes": 698514,
"comments": 24401,
"taken_at": 1779120014,
"datetime": "2026-05-18 19:00:14",
"hours_since_post": 1111,
"time_ago": "2 months ago",
"likes_per_hour": 629,
"comments_per_hour": 22
},
{
"likes": 468000,
"comments": 13548,
"taken_at": 1778947209,
"datetime": "2026-05-16 19:00:09",
"hours_since_post": 1159,
"time_ago": "2 months ago",
"likes_per_hour": 404,
"comments_per_hour": 12
},
{
"likes": 526594,
"comments": 24411,
"taken_at": 1777737719,
"datetime": "2026-05-02 19:01:59",
"hours_since_post": 1495,
"time_ago": "2 months ago",
"likes_per_hour": 352,
"comments_per_hour": 16
},
{
"likes": 462652,
"comments": 14233,
"taken_at": 1777580305,
"datetime": "2026-04-30 23:18:25",
"hours_since_post": 1538,
"time_ago": "2 months ago",
"likes_per_hour": 301,
"comments_per_hour": 9
}
]
},
"credits_used": 5,
"credits_remaining": 9999,
"request_id": "req-8Kq2ZmR4vT9xLb3P",
"cached": false
}Example captured from the Instagram API. Every SocialCrawl endpoint returns this same unified schema, so your Universal Search Multi response has the same fields.
How does the Universal Search Multi API work?
Send a GET request with your API key and get back clean, structured JSON in our unified schema. Supported computed fields are populated when the source provides the required inputs.
Method
GET
Response
JSON
How do you scrape social media data in seconds?
The fastest social media scraping API for developers. Scrape profiles, posts, comments, and analytics from 67 platforms covering 10B+ monthly active users.
One schema, every platform
Query 67 platforms with identical response structures. Write your integration once.
Computed fields, not just scraped
When an endpoint supports these metrics and the source provides the required inputs, the normalized record includes engagement_rate, estimated_reach, content_category, and language. Ready to use.
See your data before you code
Visual Data Explorer. Paste any URL, get rich result cards, sortable tables, CSV export.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}Ready to scrape Universal Search Multi data?
Get your API key and start pulling Universal Search data in under 60 seconds.
