/tencentvideo/videos/comments

POST /api/tencentvideo/videos/comments

Price: 10 credits

Get the fan discussion posts shown under a Tencent Video video: text, author, time, province, photos, likes, replies and views, with a preview of the replies

How to use it

Posts come in the site's recommended order. `replies` is a preview and `reply_count` the full total. `video_id` names the episode a post is attached to, which can differ from the requested one.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• video string required — Video id (vid) or a Tencent Video play page URL (examples: "x00174aq5no", "https://v.qq.com/x/cover/53q0eh78q97e4d1/x00174aq5no.html"; minLength: 1)
• count integer required — Max number of posts to return (min: 1; max: 1000)

Response

• @type string (default: "TencentvideoComment")
• id string required
• text string nullable
• author object nullable
  • @type string (default: "TencentvideoCommentAuthor")
  • id string required
  • name string nullable
  • image string nullable
• published_at integer nullable
• location string nullable
• images array (default: [])
• like_count integer nullable
• reply_count integer nullable
• view_count integer nullable
• share_count integer nullable
• topics array (default: [])
• video_id string nullable
• video_title string nullable
• cover_id string nullable
• community_name string nullable
• replies array (default: [])
  • @type string (default: "TencentvideoCommentReply")
  • id string required
  • text string nullable
  • author object nullable
    • @type string (default: "TencentvideoCommentAuthor")
    • id string required
    • name string nullable
    • image string nullable
  • published_at integer nullable
  • like_count integer nullable
  • reply_count integer nullable
  • location string nullable
  • parent_id string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No video exists for the given id. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.