DataXAPI
API by DataXAPI · rest
Market data over one interface: every capability takes the same parameter names, answers in the same envelope and fails with the same error structure. One call fetches one page and is charged on its own. Reads are GET; a request with a list of IDs or terms is a POST with a JSON body. The catalog (GET /v1/catalog, no key) carries the same contract with prices in force, in English and Chinese.
Endpoint: https://api.dataxapi.com/
Verification: observed. Source: crawl.
Capabilities (256)
- The balance this key's budget and scopes the rate limits
- Bilibili user videos (backup)
- Bilibili comment replies
- Bilibili hot searches
- Bilibili user profile
- Bilibili user videos
- Bilibili video comments
- Bilibili video detail
- Bilibili video search
- Bilibili popular videos
- What an idempotency key stands for right now
- What became of a call and what it was charged
- The saved result of a call again in any view
- The whole catalog: capabilities objects parameters errors prices
- One line per capability with prices and what is up right now
- One capability's whole contract
- The error codes
- The returned objects and their fields
- Find a capability from a need in words
- What is up right now the incidents on record and the share of the last 30…
- The tasks
- Douyin user videos (backup)
- Douyin video search (backup)
- Douyin comment replies
- Douyin hashtag videos