/youtube/channel

POST /api/youtube/channel

Price: 1 credit

Get YouTube channel details

How to use it

Get YouTube channel details by URL, @handle, or channel ID. Includes subscriber/video/view counts, description, links, and join date.

timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
channel string required — YouTube channel URL, @handle, or channel ID (examples: "@MrBeast", "https://www.youtube.com/@MrBeast", "UCX6OQ3DkcsbYNE6H8uQQuVA"; minLength: 1)

@type string (default: "service__parsers__youtube__channel__channel__YoutubeChannel")
id string required
name string nullable
alias string nullable
description string nullable
subscriber_count integer nullable
video_count integer nullable
view_count integer nullable
image string nullable
banner string nullable
joined_at integer nullable
country string nullable
is_verified boolean (default: false)
is_family_safe boolean nullable
links array (default: [])
- @type string (default: "YoutubeChannelLink")
- url string required

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 — Channel not found. Verify the channel URL, handle, or 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.

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.