POST /api/kick/channels
Price: 1 credit
Get Kick channel details by slug or URL
Get full details of a Kick channel by slug or channel URL. Returns username, avatar, banner, bio, follower count, verified/affiliate status, social links, recent stream categories, chat settings, and the current live stream (title, category, viewer count) if broadcasting.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)slug string required — Kick channel slug (e.g. 'xqc') or channel URL (examples: "xqc", "https://kick.com/xqc"; minLength: 1)@type string (default: "KickChannel")id integer requireduser_id integer requiredalias string requiredusername string nullableurl string requiredbio string nullableimage string nullablebanner string nullableoffline_banner string nullablefollower_count integer (default: 0)is_banned boolean (default: false)is_verified boolean (default: false)is_affiliate boolean (default: false)subscription_enabled boolean (default: false)vod_enabled boolean (default: false)can_host boolean (default: false)is_muted boolean (default: false)playback_url string nullablesocials object nullable@type string (default: "KickSocials")instagram string nullabletwitter string nullableyoutube string nullablediscord string nullabletiktok string nullablefacebook string nullablerecent_categories array (default: [])@type string (default: "KickCategory")id integer requiredalias string requiredname string requiredurl string requireddescription string nullableimage string nullableis_mature boolean (default: false)is_promoted boolean (default: false)viewer_count integer (default: 0)follower_count integer (default: 0)tags array (default: [])parent object nullable@type string (default: "KickParentCategory")id integer nullablename string nullablealias string requiredicon string nullablechatroom object nullable@type string (default: "KickChatroom")id integer requiredchat_mode string nullableslow_mode boolean (default: false)followers_mode boolean (default: false)subscribers_mode boolean (default: false)emotes_mode boolean (default: false)message_interval integer (default: 0)following_min_duration integer (default: 0)created_at integer nullableupdated_at integer nullablelivestream object nullable@type string (default: "KickLivestream")id integer requiredalias string nullablesession_title string nullableis_live boolean (default: false)is_mature boolean (default: false)language string nullableviewer_count integer (default: 0)duration_seconds integer (default: 0)created_at integer nullablestarted_at integer nullableimage string nullablesource string nullabletags array (default: [])category object nullable@type string (default: "KickCategory")id integer requiredalias string requiredname string requiredurl string requireddescription string nullableimage string nullableis_mature boolean (default: false)is_promoted boolean (default: false)viewer_count integer (default: 0)follower_count integer (default: 0)tags array (default: [])parent object nullable@type string (default: "KickParentCategory")id integer nullablename string nullablealias string requiredicon string nullable422 — 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 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 identifierX-Execution-Time — Execution time in secondsX-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.