/youku/shows/channel

POST /api/youku/shows/channel

Price: 20 credits

Read the shows Youku is currently promoting on one of its channel front pages — drama, anime, variety, film, kids, or the site home. Each row carries the show id and URL, the promoted title and blurb, the episode-count label, the follower count, editorial tags, artwork and the preview video.

How to use it

This is Youku's own editorial selection for a channel, not a browsable catalogue: it answers 'what is Youku pushing right now', changes between requests, and this `channel` argument itself carries no year, genre or region filter. Rows repeat across the carousels, so a large `count` returns fewer distinct shows than asked and that is the source, not a truncation. The fields are the promo card's: `name` and `description` are marketing copy rather than the catalogue title and synopsis, and there is no cast, category or release date. Take `id` to /youku/shows for the real record.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• channel string required — Youku channel whose editorial feed to read (one of: "home", "drama", "anime", "variety_show", "movie", "kids"; examples: "drama")
• count integer required — Max number of shows to return (examples: 40; min: 1; max: 100)

Response

• @type string (default: "YoukuShow")
• id string required
• numeric_id string nullable
• name string nullable
• subtitle string nullable
• description string nullable
• url string nullable
• category string nullable
• category_id string nullable
• feature string nullable
• release_date string nullable
• episode_total integer nullable
• episode_label string nullable
• last_episode_date string nullable
• is_completed boolean (default: false)
• is_vip boolean (default: false)
• heat integer nullable
• rating number nullable
• chart string nullable
• chart_rank integer nullable
• comment_count integer nullable
• like_count integer nullable
• follower_count integer nullable
• image string nullable
• image_vertical string nullable
• package_types array (default: [])
• tags array (default: [])
• genre_labels array (default: [])
• cast array (default: [])
  • @type string (default: "YoukuCastMember")
  • id string required
  • name string nullable
  • role string nullable
  • image string nullable
• seasons array (default: [])
  • @type string (default: "YoukuSeason")
  • id string required
  • name string nullable
  • url string nullable
  • last_video_id string nullable
  • last_video_url string nullable
  • is_current boolean (default: false)
• latest_video object nullable
  • @type string (default: "YoukuVideo")
  • id string required
  • numeric_id string nullable
  • name string nullable
  • url string nullable
  • show_id string nullable
  • show_name string nullable
  • show_url string nullable
  • creator_id string nullable
  • creator_name string nullable
  • creator_url string nullable
  • category string nullable
  • video_type string nullable
  • episode_order integer nullable
  • stage string nullable
  • stage_label string nullable
  • duration integer nullable
  • image string nullable
  • publish_date string nullable
  • comment_count integer nullable
  • like_count integer nullable
  • is_vip boolean (default: false)
  • is_pinned boolean (default: false)
  • allow_comment boolean (default: false)
  • allow_download boolean (default: false)
  • allow_share boolean (default: false)
  • allow_like boolean (default: false)
  • audio_languages 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 — The entity was not found, or a precondition failed 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.