Give one YouTube search keyword and an expected count to get matching public videos, channels, view counts, and publish times.
YouTube Account Info
Collect public channel profiles, audience metrics, and contact signals for one or more YouTube accounts
Overview
YouTube channel pages mix branding, audience size, and contact details in a layout that is hard to compare across accounts. This app turns those public channel profiles into a consistent record set so research, partnership, and monitoring teams can work from the same identifiers, metrics, and timestamps.
The value is the joined profile snapshot: channel identity, displayed name, public URL, follower and view figures, location, join date, and publicly shown contact details stay together for each submitted account. That makes it easier to qualify channels, compare audience scale, and keep a watch list current without reconstructing profiles by hand.
Data notes
The data comes from the public YouTube channel profile associated with each submitted account or channel name. One record is produced for each submitted account when the source returns a profile or a no-data marker. Duplicate submitted accounts are removed across collected pages. Audience counts, location, country, join date, links, and timestamps retain the source text; a source value can be unavailable and appear empty. Timestamps are preserved as supplied, without inferring a timezone. Private, terminated, and login-only channels are outside the coverage.
What the results look like
Each record represents the public profile collected for one submitted YouTube account.
| Channel name | Channel ID | Channel URL | Submitted account | No data |
|---|---|---|---|---|
| Ulanzi Japan(ウランジ) | UCUo0_zutHjxAwHnrTHFph_g | https://www.youtube.com/@UlanziJapan | UlanziJapan | No |
| DemoChannel | Yes |
Additional values include Source keyword, Business ID, Public email, Follower count, Raw follower text, Location, Country, Joined date, Profile links, View count, Video count, Source updated at, and Collected at.
Use cases
- Qualify partnership targets by comparing Channel name, Channel ID, and Follower count across a watch list.
- Map public presence by lining up Channel URL, Location, Country, and Joined date for channels you already monitor.
- Separate empty outcomes from usable profiles by checking No data together with Submitted account before using View count or Video count.
- Keep a collection log by comparing Source updated at with Collected at when the same Submitted account is reviewed again.
Scope and boundaries
Each run accepts 1 to 200 YouTube accounts or channel names and returns public profile records when data is available.
- Good for
- When you need a current public profile snapshot for specific YouTube channels
- When you need displayed audience size, location, join date, and public contact details in one record
- Do not use for
- When you need video lists, comments, or search results rather than channel-level profile information
- When you do not have a YouTube account or channel name to collect
Failure handling
Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.
- 1If no profile data is returned, verify the account or channel name and confirm the channel is still public
- 2Retry later after rate limiting, temporary unavailability, or a timeout
- 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
- 4If authentication fails, verify the API Key configured for the execution environment
Input
Parameters required to call this App, generated from the input.schema in manifest.json.
- YouTube account list
itemsRequiredarray<object>The YouTube accounts or channel names to collect. Submit 1 to 200 items; each item needs an account value and whether to collect extra details.Itemsup to 200 itemsExample[{"account":"UlanziJapan","needMoreInfo":true}]
Output
Field structure of a single record, generated from the output.schema in manifest.json.
- Submitted account
task_itemstringThe account or channel name submitted for this recordExampleUlanziJapan - No data
no_databooleanWhether this submitted account returned no public profileExamplefalse - Source keyword
keywordstringThe source keyword associated with the collected accountExampleUlanziJapan - Channel ID
account_idstringThe YouTube channel identifier returned for the profileExampleUCUo0_zutHjxAwHnrTHFph_g
Sample data
Generated from output.schema. Fields without a sample value use structural placeholders.
{
"task_item": "UlanziJapan",
"no_data": false,
"keyword": "UlanziJapan",
"account_id": "UCUo0_zutHjxAwHnrTHFph_g",
"account_name": "Ulanzi Japan(ウランジ)",
"account_home_url": "https://www.youtube.com/@UlanziJapan",
"biz_id": "UlanziJapan",
"email": "<email>",
"fans_count": "<fans_count>",
"fan_nums_origin": "<fan_nums_origin>",
"location": "<location>",
"country": "<country>",
"joined_date": "<joined_date>",
"links": "[]",
"views_num": "<views_num>",
"publish_content_count": "<publish_content_count>",
"clean_update_time": "2026-08-27T14:19:57",
"crawl_time": "2026-08-27T14:19:57"
}Integration
This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.
With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.
Client config
Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=hello_moto/youtube-account-info",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Let AI set it up for you
Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)
detail.access.mcp.composeHint
Pricing
Charged once per submitted run, regardless of how many records are returned.
Charged by the number of records successfully returned. Failed runs are not charged.
Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.
View creditsTry it now
Fill in the parameters and run. Results come from a real call.