YouTube Channel ID Extractor
Pricing
from $2.99 / 1,000 channel identities
YouTube Channel ID Extractor
Resolve public YouTube channel identities from handles, UC IDs, canonical URLs, legacy /user URLs, and public video owners with source provenance.
Pricing
from $2.99 / 1,000 channel identities
Rating
0.0
(0)
Developer
w3crawler
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
Resolves public YouTube channel identities from channel handles, channel IDs, channel URLs, public video URLs, or public video IDs. A video reference is followed to the public owner metadata and, when available, the owner About page is read for richer public statistics.
The actor uses public HTML and embedded page metadata only. It does not require login, cookies, private endpoints, browser automation, or signed media URLs.
Input
| Field | Description |
|---|---|
channelUrls | Public channel references; public video URLs are accepted for compatibility. |
videoUrls | Public /watch, /shorts, /live, or youtu.be URLs. |
videoIds | Public 11-character video IDs. |
maxItems | Maximum references, from 1 to 200 (default 50). |
includeDiagnostics | Store safe diagnostics for failed or blocked public pages (default true). |
enableProxyFallback | Try ordinary Apify Proxy after direct access fails (default true). |
maxRetries, requestDelayMs, requestTimeoutSecs | Bounded request controls. |
proxyConfiguration | Optional credential-free Apify Proxy settings. |
Example:
{"channelUrls": ["@GoogleDevelopers"],"videoIds": ["dQw4w9WgXcQ"],"maxItems": 2,"includeDiagnostics": true,"enableProxyFallback": false,"proxyConfiguration": {"useApifyProxy": false}}
Output
Each identity record contains the original reference and type, channel ID/name/handle/canonical URL, description, avatar/banner, displayed and parsed subscriber/total-view/video counts, join date, country, keywords, external links, optional source video ID, resolution method, source page, extraction method, and scrapedAt. Unavailable fields are omitted.
The default dataset also receives safe diagnostics when requested. OUTPUT records item counts, failures, blocks, duration, and whether Apify Proxy routing was requested and configured. Operational request details, credentials, cookies, proxy URLs, and private data are never written.
Development
npm cinpx apify validate-schema .actor/input_schema.jsonnpm testapify run --purge --input-file qa-inputs/youtube-channel-id-extractor/local-validation.jsonnpm run validate-dataset
The cloud-validation.json fixture explicitly requests the ordinary US Apify Proxy group for a genuine server routing check.