/tencentvideo/covers

POST /api/tencentvideo/covers

Price: 10 credits

Get a Tencent Video series, film or show by cover id: titles, synopsis, genres, themes, area, year, rating with its count, star distribution and reviews, heat, cast with roles, language versions, episode and video counts, and the ids of its videos and clips

How to use it

A cover id (cid) is the 15-character id in a v.qq.com/x/cover/ URL; a video id (vid) is rejected here. `video_ids` lists the cover's episodes and extras - use tencentvideo/covers/episodes for the ordered episode list. `clip_ids` are the clips on the cover page's first clip rail page, none of them in `video_ids`; `default_video_id` is the video the cover page opens on; `reviews` are the rating reviews shown on the cover page.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• cover string required — Cover id (cid) or a Tencent Video cover page URL (examples: "mzc00200803dr6b", "https://v.qq.com/x/cover/mzc00200803dr6b/c4102g9a01t.html"; minLength: 1)

Response

• @type string (default: "TencentvideoCover")
• id string required
• url string required
• subtitle string nullable
• description string nullable
• aliases array (default: [])
• category string nullable
• category_id string nullable
• main_genre string nullable
• sub_genre string nullable
• area string nullable
• year integer nullable
• published_date integer nullable
• online_at integer nullable
• episode_count integer nullable
• video_count integer nullable
• update_notice string nullable
• score number nullable
• rating_count integer nullable
• rating_distribution array (default: [])
  • @type string (default: "TencentvideoRatingShare")
  • stars integer required
  • label string nullable
  • share number nullable
• reviews array (default: [])
  • @type string (default: "TencentvideoCoverReview")
  • id string required
  • text string nullable
  • rating integer nullable
  • rating_label string nullable
  • tags array (default: [])
  • like_count integer nullable
  • author_name string nullable
  • author_image string nullable
  • watch_time_label string nullable
• douban_score number nullable
• imdb_score number nullable
• imdb_id string nullable
• heat integer nullable
• view_count integer nullable
• reservation_count integer nullable
• is_free boolean nullable
• pay_status string nullable
• access_label string nullable
• leading_actors array (default: [])
• guests array (default: [])
• cast array (default: [])
  • @type string (default: "TencentvideoCastMember")
  • id string required
  • name string nullable
  • role string nullable
  • image string nullable
  • user_id string nullable
• keywords array (default: [])
• tags array (default: [])
• themes array (default: [])
• tagged_people array (default: [])
• language_versions array (default: [])
  • @type string (default: "TencentvideoLanguageVersion")
  • language string required
  • cover_id string nullable
  • video_id string nullable
  • is_current boolean (default: false)
• audience_age string nullable
• column_id string nullable
• column_title string nullable
• community_id string nullable
• image string nullable
• banner string nullable
• default_video_id string nullable
• video_ids array (default: [])
• clip_ids array (default: [])

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 cover 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.