Does LargitData provide APIs for Weibo, Xiaohongshu, Douyin and Threads?

Yes. All four platforms have commercial endpoints; this hub links to each platform's endpoint table, workflow, curl examples and samples. Data is collected by web crawlers from content publicly published on each platform.

How does authentication work?

Send your API key in the auth-header request header on every call. The base URL is https://api.infominer.io/api/v2. How keys are provided is confirmed when you request a trial.

Why create a task and then poll it?

Collection takes time, so the API is asynchronous: POST creates a task and returns its id, GET polls it, and you read the results once the status is DONE.

How much history is available?

Confirmed per project scope. Where the snapshot states a range it is on the platform page, for example the 30-day backfill when you subscribe a Weibo translation keyword.

Where is the full parameter reference?

api.infominer.io/docs has the full API documentation. The platform pages on this site summarize the published endpoints and the actual workflow so you can judge fit quickly.

Social Media API reference: Weibo, Xiaohongshu, Douyin and Threads

Based on the 2026-10-25 specification snapshot

Quick answer

The LargitData Social Media API serves data from Weibo, Xiaohongshu, Douyin and Threads, collected by web crawlers from content publicly published on each platform. The commercial endpoints live at https://api.infominer.io/api/v2 and authenticate with an API key in the auth-header request header. Collection endpoints are asynchronous: create a task, poll it by task ID, then read the results. This hub and the four platform pages are written from the 2026-10-25 specification snapshot; the full reference is at api.infominer.io/docs.

Four platforms

Platform	Data available	Published endpoints
Weibo API reference	Keyword search, comments, reposts, repost-chain tracing, public account timelines, and English machine translation of posts, comments and reposts for subscribed English keywords.	13
Xiaohongshu API reference	Keyword search of notes, note comments with second-layer replies, and public account timelines.	6
Douyin API reference	Keyword search of videos, video comments, public account timelines, and download-URL resolution for collected videos (redirect only).	7
Threads API reference	Keyword search, post replies, public account timelines and post reactions tasks, with optional masking of author fields.	8

How to get the data

Request a trial; once we confirm the scope you receive an API key, then send it in the auth-header header on every request.
POST to create a task, for example a keyword search, the comments of one post or a public account timeline. The response carries the task id and a status (INIT in the snapshot example).
GET the task by id to poll it. Status values depend on the endpoint: typically INIT, RUNNING, DONE and FAILED, with PARTIAL and TIMED_OUT on some endpoints. Read results at DONE; stop and handle the failure at FAILED.
For Weibo, Xiaohongshu and Douyin search, comment and repost tasks, the poll response of a DONE task carries the data, paged with page and pageSize; timeline and repost-chain polls take no paging parameters. Threads retrieval is described on the Threads page.
Weibo translation works by keyword subscription: a background backfill job runs for each subscription, and reading translated posts, comments and reposts needs no task, only a query on the subscribed keywords.

Authentication and curl

Base URL: https://api.infominer.io/api/v2. Send your API key in the auth-header request header. The example below uses Weibo keyword search: create a task, then poll it by task ID.

curl -X POST https://api.infominer.io/api/v2/weibo/search/task \
  -H "auth-header: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keyword": "手冲咖啡", "start_date": "2026-06-01", "end_date": "2026-06-30", "max_pages": 3}'

curl "https://api.infominer.io/api/v2/weibo/search/task/$TASK_ID?page=1&pageSize=100" \
  -H "auth-header: YOUR_API_KEY"

How posts and comments link

Comment and reply tasks are created from a post URL (post_url). On Weibo, Xiaohongshu and Douyin, comment records link back to their post through the post_id field; Weibo repost records also have a parent_id field pointing at the reposted post, and the repost chain can be traced upward (depth up to 10). Threads reactions tasks are also created from post_url and return the reactions list for that post when they are DONE and neither partial nor timed out.

History and limits

How far back you can go, how much you can collect per task and how often data refreshes are confirmed per project scope.
Limits that the snapshot states explicitly are listed on each platform page, for example the 30-day backfill for Weibo translation, the default of 50 comments per Douyin video, and Threads search polls that carry no results.
Page-size caps vary by endpoint, for example 100 for keyword search results, 1000 for comments and 1000 per_page for Threads reactions.

Collection: web crawlers collect content publicly published on each platform. Whether this suits your use depends on the purpose and jurisdiction and is for the buyer's legal team to assess; we can provide a description of sources and collection methods.

Delivery format

Responses are JSON. Field structures differ by platform, so use each platform page's field table and samples. Batch files or other delivery methods are confirmed per project scope.

Request a trial

Tick the platforms in the form below and tell us the keyword or account scope, expected volume and delivery format. We confirm the scope and reply with the arrangements for the trial, API key and integration.

FAQ

Does LargitData provide APIs for Weibo, Xiaohongshu, Douyin and Threads?: Yes. All four platforms have commercial endpoints; this hub links to each platform's endpoint table, workflow, curl examples and samples. Data is collected by web crawlers from content publicly published on each platform.
How does authentication work?: Send your API key in the auth-header request header on every call. The base URL is https://api.infominer.io/api/v2. How keys are provided is confirmed when you request a trial.
Why create a task and then poll it?: Collection takes time, so the API is asynchronous: POST creates a task and returns its id, GET polls it, and you read the results once the status is DONE.
Is it legal to collect data this way?: It depends on the purpose and jurisdiction, and is for the buyer's legal team to assess. We can provide a description of sources and collection methods.
How much history is available?: Confirmed per project scope. Where the snapshot states a range it is on the platform page, for example the 30-day backfill when you subscribe a Weibo translation keyword.
Where is the full parameter reference?: api.infominer.io/docs has the full API documentation. The platform pages on this site summarize the published endpoints and the actual workflow so you can judge fit quickly.