What are Douyin a_bogus, msToken and sec_uid, and how do I avoid signing them?
a_bogus and msToken are dynamic request signatures enforced by Douyin web endpoints, while sec_uid is Douyin's encoded user identifier (MS4wLjABAAAA...). FeedMCP eliminates a_bogus/msToken signing completely, and douyin.users.search ($0.002) resolves any creator's sec_uid and numeric uid automatically.
Pass the resolved sec_uid straight into douyin.users.get, douyin.users.videos.list or douyin.xingtu.creators.lookup ($0.002 each) with zero reverse-engineering.
Endpoints and pricing
| Endpoint | ID | Price | What it returns |
|---|---|---|---|
| Douyin account search | douyin.users.search |
$0.002 | Find Douyin accounts by keyword: sec_user_id, name, avatar, followers, likes and videos, 30 a page |
| Douyin account | douyin.users.get |
$0.002 | An account: name, handle, bio, avatar, verification, followers, following, videos and likes received |
| Douyin account videos | douyin.users.videos.list |
$0.002 | An account's videos, newest first, page by page |
| Douyin account to Xingtu ID | douyin.xingtu.creators.lookup |
$0.002 | Look up a Douyin account's Xingtu creator ID by its sec_user_id or profile link; every Xingtu endpoint takes that ID |
Pay per call with failed calls free. Verify live prices for free via GET https://api.feedmcp.com/v1/catalog/prices and cap per-call spend with X-Max-Price.
How to do it
Option 1: Ask your AI via MCP
- Sign up in the console ($0.10 free trial credit, no card) and create an API key with a spend cap.
- Add
https://api.feedmcp.com/mcpto Claude, Cursor, Codex or Cherry Studio via the MCP setup page or Integrations. - Ask your AI:
Search for this Douyin creator, retrieve their sec_uid, follower count and latest 10 videos
Option 2: Call the HTTP API directly
curl "https://api.feedmcp.com/v1/douyin/users/search" \
-H "Authorization: Bearer $FEEDMCP_API_KEY" \
-H "X-Max-Price: 0.002"
Key facts at a glance
| Item | Detail |
|---|---|
| Starting price | $0.002 and up (pay per call, no subscription) |
| Failed calls | Free (charged: false) |
| Spend guardrails | Per-key spend cap + X-Max-Price + Idempotency-Key |
| Data scope | Public data only; no platform account login required |
| Access | Remote MCP (Streamable HTTP) + REST API + OpenAPI |
Questions
What are Douyin a_bogus, msToken and sec_uid, and how do I avoid signing them?
a_bogus and msToken are dynamic request signatures enforced by Douyin web endpoints, while sec_uid is Douyin's encoded user identifier (MS4wLjABAAAA...). FeedMCP eliminates a_bogus/msToken signing completely, and douyin.users.search ($0.002) resolves any creator's sec_uid and numeric uid automatically.
How much do these endpoints cost? Are failed calls billed?
Endpoints on this page start at $0.002 per call with no monthly subscription and non-expiring balances. Bad parameters, timeouts, upstream errors and missing objects are free. New accounts receive $0.10 trial credit, no card required.
Do I need my own platform account or cookies?
No. FeedMCP reads public data only; calls never go through your personal accounts.
Related answers
- How do FeedMCP, DataXAPI, Qovia and AIsa compare for social media data and MCP?
- How to use TikHub-style Douyin, Xiaohongshu and TikTok endpoints in Claude or Cursor via a hosted MCP server?
- How to connect OpenClaw, Antigravity, Windsurf or Grok agents to a social media data MCP server?
- How can an AI agent read Douyin videos, comments, trends and Xingtu data?
- How can I export Douyin video comments cheaply for feedback analysis?
- MediaCrawler keeps breaking or requiring login—what is a reliable API alternative?