channel_info
string
required
A channel id (UC…) or a handle (@mrbeast or bare mrbeast). Handles are resolved for you and cached.
Resolve a channel handle ⇄ id. YouTube hides the channel id, so turn the @handle you have into the id the API needs.
Send a handle (@mrbeast or bare mrbeast) or a channel id (UC…) and get back the canonical {channel_id, handle, title}. Free, and the mapping is cached, so it stays fast. Every channel endpoint also accepts a handle directly; this endpoint is for when you just need the id itself.
/api/v1/channel/lookup
Free
Use your Tubefield API key instantly, or inspect the sample response first.
curl -X POST https://tubefield.com/api/v1/channel/lookup \
-H "Content-Type: application/json" \
-H "X-API-Key: $TUBEFIELD_API_KEY" \
-d '{"channel_info": "@mrbeast"}'
Sample response
{
"channel_id": "UCX6OQ3DkcsbYNE6H8uQQuVA",
"handle": "@mrbeast",
"target": "@mrbeast",
"title": "MrBeast"
}
Run a real /api/v1/channel/lookup request. No key? We show the real sample result so you can still inspect the shape.
Endpoint
POST /api/v1/channel/lookup
X-API-Key
Free
Leave empty to inspect the response shape without spending API balance.
Sample mode: explore the real response shape for free. Add a key to run a live request.
Response
POST /api/v1/channel/lookup
{
"channel_id": "UCX6OQ3DkcsbYNE6H8uQQuVA",
"handle": "@mrbeast",
"target": "@mrbeast",
"title": "MrBeast"
}
The full contract for /api/v1/channel/lookup: what to send and what comes back.
channel_info
string
required
A channel id (UC…) or a handle (@mrbeast or bare mrbeast). Handles are resolved for you and cached.
| Field | Type | Description |
|---|---|---|
channel_id |
string | null | Canonical channel id (UC…), or null when the input resolves to no channel (still a free, billable 200). |
handle |
string | null | The channel's handle (e.g. @mrbeast) when known. |
title |
string | null | Channel title when known. |
Copy, paste, swap in your API key.
curl -X POST https://tubefield.com/api/v1/channel/lookup \
-H "Content-Type: application/json" \
-H "X-API-Key: " \
-d '{"channel_info": "@mrbeast"}'
Common ways Channel Lookup ends up in production.
Turning a YouTube @handle into the channel id the API needs.
Normalising user-pasted channel handles before a batch job.
Confirming a channel's canonical id and handle in one call.
The same predictable contract on every endpoint.
200 |
Success. The lookup completed and was charged, even if the response is empty. |
401 |
Missing or unknown API key. |
402 |
Not enough balance on the account. |
422 |
Invalid request body (wrong shape or types). |
429 |
Rate limit exceeded: max 10 requests per second per API key. |
Explore the rest of the YouTube API.
Video Detail
/api/v1/video/detail
Video Comments
/api/v1/video/comments
Video Transcript
/api/v1/video/transcript
Channel Detail
/api/v1/channel/detail
Channel Videos
/api/v1/channel/videos
Channel Playlists
/api/v1/channel/playlists
Playlist Detail
/api/v1/playlist/detail
Playlist Videos
/api/v1/playlist/videos
Video Search
/api/v1/search/videos
Search Result (SERP)
/api/v1/search/result
Account Balance
/api/v1/account/balance
New accounts start with a free API balance. Paid balance never expires, so it can sit until your workflows need it.
$0.50 free
$0.50 free balance to start. About 150 standard requests. Get an API key in seconds with no credit card.
$10 one-time
Adds $10 to your API balance for steady production traffic and early automated jobs.
$100 one-time
$130 spendable balance, including a $30 bonus. The sweet spot for production workloads.
Start with a free key and about 150 free requests, on REST, MCP, or both.