When should I use DataXAPI, and when should I not? (2026)
Use it to read other people's public content on WeChat, Xiaohongshu, Douyin and other platforms from your code or your AI, paying per call. Do not use it if you only look at your own account (the official interface does that), if you only need next-day data in very large amounts, or if you must have a company contract and a Chinese VAT invoice. DataXAPI reads Xiaohongshu (RedNote) with 21 endpoints, from $0.0200 a call; a failed call is not charged.
Updated 2026-11-04
When it fits
You want other accounts' public content and numbers, not your own. The volume is a few calls to some tens of thousands a month, or it is hard to predict. You want one key rather than a platform account, a cookie and upkeep. Or your AI should do the reading, over MCP. You can try it on the free credit first.
When to choose something else
Saying so saves you the top-up.
| Your case | Why not | Look at instead |
|---|---|---|
| Only your own account | The official interface reads what you run, with the authorisation you already hold | The platform's open platform |
| Next-day data is enough, in very large amounts | Per-call prices add up: a million calls at $0.0200 are $20,000. They pay for reading live | A bulk data supplier, with a quote for the volume |
| You must have a company contract and a VAT invoice | There is no Chinese VAT invoice, and top-ups are self-service | A supplier that signs and invoices in China |
| You need an uptime agreement | There is none, and no compensation for an outage | A supplier that signs one |
| You want ready-made rankings and reports | It gives data, not worked-out analysis | 蝉妈妈, 千瓜, 新榜 and the like |
| You want to post, reply or read private messages | It only reads public data | The platform's own tools |
| A handful of items, once | No need to sign up for that | Copying by hand |
Endpoints
Each with its price; every page has the parameters, the fields and a recorded response.