/rutube/videos/category

POST /api/rutube/videos/category

Price: 20 credits

List videos in a category

How to use it

List the latest videos in a Rutube category by its numeric id. Returns videos with title, author channel, view count, duration, and timestamps.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• category integer required — Category numeric id (examples: 17; min: 1)
• count integer required — Max result count (examples: 20; min: 1)

Response

• @type string (default: "RutubeVideo")
• id string required
• description string nullable
• url string nullable
• image string nullable
• preview_url string nullable
• author object nullable
  • @type string (default: "RutubeAuthor")
  • id integer required
  • name string nullable
  • image string nullable
  • url string nullable
  • is_official boolean (default: false)
  • subscriber_count integer nullable
• category object nullable
  • @type string (default: "RutubeCategory")
  • id integer required
  • name string nullable
  • alias string nullable
  • url string nullable
• pg_rating object nullable
  • @type string (default: "RutubePgRating")
  • age integer nullable
  • image string nullable
• duration integer nullable
• view_count integer nullable
• track_id integer nullable
• embed_url string nullable
• origin_type string nullable
• tags array (default: [])
  • @type string (default: "RutubeTag")
  • id integer required
  • name string nullable
  • url string nullable
• restricted_countries array (default: [])
• is_adult boolean (default: false)
• is_official boolean (default: false)
• is_licensed boolean nullable
• is_livestream boolean (default: false)
• is_on_air boolean (default: false)
• is_audio boolean (default: false)
• is_paid boolean (default: false)
• is_serial boolean (default: false)
• created_at integer nullable
• published_at integer nullable
• updated_at integer 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 — Category not found 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.