/tencentvideo/covers/episodes

POST /api/tencentvideo/covers/episodes

Price: 10 credits

List the episodes and previews of a Tencent Video series, show or film as its cover page lists them: video id, episode number, title, duration, trailer flag, access label, language and thumbnail

How to use it

Previews are listed beside the episodes and marked by `is_trailer`; filter on it for episodes only. Short-drama and short-anime covers list their videos in order. A cover with no videos of its own, such as a title hosted on another site, returns an empty list. Each `id` is a video id for tencentvideo/videos and tencentvideo/videos/comments.

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/53q0eh78q97e4d1.html"; minLength: 1)
• count integer required — Max number of episodes to return (min: 1)

Response

• @type string (default: "TencentvideoEpisode")
• id string required
• url string required
• cover_id string required
• episode string nullable
• short_title string nullable
• full_title string nullable
• subtitle string nullable
• duration integer nullable
• is_trailer boolean nullable
• access_label string nullable
• published_date integer nullable
• language string nullable
• subtitle_languages array (default: [])
• aspect_ratio number nullable
• image 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 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.