DataNavoAPI / ROLES

Comment replies

Comment replies. Follow concrete contracts, examples and reviewable steps using Douyin, Bilibili, Kuaishou, Instagram.

LOCAL SIMULATIONAll displayed records are fictional fixtures. Live APIs, payments and external email are disabled.中文版 ↗
01

One task, distinct platform contracts

Comment replies links 10 capabilities. Each contract still defines identifiers, pagination, missing fields and result counts; compare the contracts before merging tables.

CapabilityObjectShapePagination
douyin.comments.replies.listCommentitemsExplicit cursor
bilibili.comments.replies.listCommentitemsExplicit cursor
kuaishou.comments.replies.listCommentitemsExplicit cursor
instagram.comments.replies.listCommentitemsExplicit cursor
tiktok.comments.replies.listCommentitemsExplicit cursor
weibo.comments.replies.listCommentitemsExplicit cursor
xiaohongshu.comments.replies.listCommentitemsExplicit cursor
youtube.comments.replies.listCommentitemsExplicit cursor
wechat_channels.comments.replies.listCommentitemsExplicit cursor
zhihu.comments.replies.listCommentitemsExplicit cursor
02

Cross-platform alignment

  • Use platform and object ID together as the key.
  • Align observation windows and time zones while preserving capture times.
  • Matching field names do not guarantee matching definitions; record missing values explicitly.
TRY THE CONTRACT

Clear inputs. Inspectable output.

Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.

Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.

Download contract example (no execution) ↗

For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗