/tencentvideo/videos

POST /api/tencentvideo/videos

Price: 1 credit

Get a Tencent Video video (an episode, trailer or clip) by video id: title, episode number, duration, upload time, the cover it belongs to, and its thumbnail

How to use it

A video id (vid) is the 11-character id at the end of a v.qq.com/x/cover/<cid>/<vid>.html URL; a cover id is rejected here. `cover_id` leads to tencentvideo/covers for the series or film it belongs to.

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: "c4102g9a01t", "https://v.qq.com/x/cover/mzc00200803dr6b/c4102g9a01t.html"; minLength: 1)

Response

• @type string (default: "TencentvideoVideo")
• id string required
• url string required
• subtitle string nullable
• episode string nullable
• episode_title string nullable
• description string nullable
• category string nullable
• category_id string nullable
• duration integer nullable
• intro_end_seconds integer nullable
• outro_start_seconds integer nullable
• is_trailer boolean nullable
• cover_id string nullable
• cover_ids array (default: [])
• uploaded_at integer nullable
• released_at integer nullable
• topics array (default: [])
• 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 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.