API Reference
Priority Channel Resolve
Resolve a YouTube channel identifier from input (ID, handle, or URL).
POST /v1/priority/channel
Use this endpoint when you need data fast on a single YouTube channel.
This is a real-time lookup, designed for customer-facing workflows where delays aren’t acceptable.
Best For
- Enriching a YouTube channel as part of a sign-up flow
- Powering a real-time pricing or scoring tool
- Responding instantly to customer input (e.g. form submission, or a request for channel contact info)
How It Works
- Takes one YouTube channel ID per request
- Returns channel data in ~ seconds
- Results include performance metrics, summary data, and optionally email if requested
- Uses premium credits – designed for speed, not scale
🧪 Example Request
curl -X POST https://api.channelcrawler.com/v1/priority/channel \
-H "Authorization: Bearer $CC_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"channel_id": "UCX6OQ3DkcsbYNE6H8uQQuVA",
"fields": {
"include_email": true
}
}'Request Parameters:
channel(string, optional): YouTube channel handle or URLchannel_id(string, optional): YouTube channel ID- At least one of
channelorchannel_idmust be provided
- At least one of
fields(object, optional): Fields to include in the responseinclude_email(boolean, optional): Whether to include email address in response (default:true)
💳 Credit Usage
| Condition | Credits Charged |
|---|---|
| Channel data only | 0.5 (premium rate) |
| Channel + Email (when available) | 5.0 (premium rate) |
Important Notes:
- If
fields.include_emailis not set or isfalse:- You are charged
0.5credits - Email address is stripped from the response even if available in the database
- You are charged
- If
fields.include_emailistrue:- You are charged
5.0credits only if the channel has an email address - You are charged
0.5credits if the channel does not have an email address
- You are charged
- Credits are deducted immediately upon successful response
📤 Response
The response includes:
channel_id: The resolved YouTube channel IDresolved_by: How the channel was identified (e.g., by ID, handle, or URL)present: Whether the channel was already in the databaseresult: The channel data object (includes email only if requested and available)cost: Cost information objecttotal: Credits charged for this request
Example Response:
{
"channel_id": "UCX6OQ3DkcsbYNE6H8uQQuVA",
"resolved_by": "channel_id",
"present": true,
"result": {
"channel_id": "UCX6OQ3DkcsbYNE6H8uQQuVA",
"profile": {
"title": "MrBeast",
"email": "[email protected]"
}
},
"cost": {
"total": 5.0
}
}Tip: Use for real-time UX
This endpoint is best used in-the-moment, not in batch.
If you're trying to enrich or discover lots of channels, use our standard /v1/channels/search endpoint or the Imports system instead.