Channel due diligence
Collect public channel details, video lists, and posting surfaces for creator vetting or media research.
Create YouTube analytics, content research, and channel monitoring products with API API methods for profiles, videos, shorts, playlists, posts, comments, and search.
ScrapeStorm is not affiliated with YouTube. Process data only where you have a valid business and legal basis.
YouTube teams usually evaluate channel research, content monitoring, and video discovery first. These workflows connect common product needs to concrete API surfaces.
Collect public channel details, video lists, and posting surfaces for creator vetting or media research.
Monitor videos, shorts, playlists, posts, and comments for reporting and content operations.
Search channels and content by query or country to understand trends across markets.
Pair video details with comments and publishing surfaces to support reporting or editorial analysis.
Use channel and content API methods to keep creator records current inside media, influencer, or CRM products.
Browse every supported YouTube entity below, understand what each surface is for, and open the exact docs that matches your workflow.
Profile API methods resolve public identity, account context, and the base layer for creator, brand, or people-oriented products.
What you get. Use this entity to fetch account details, contacts, summary context, and the identifiers you need before moving into content or social API methods.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Start here when you need richer public context behind profile: About by user identifier and want the most complete identity view first.
Use these docs to work with profile: Shorts by user identifier when your product needs a clear API method into public profile workflows.
Choose this API method when your product needs a compact performance view around profile without opening a larger content collection.
Open these docs when you need the actual profile content surface for monitoring, archive jobs, or reporting workflows.
Open these docs when you need the actual profile content surface for monitoring, archive jobs, or reporting workflows.
Choose this API method when your product needs a compact performance view around profile without opening a larger content collection.
Playlist API methods help you navigate grouped content collections and the sequencing behind them.
What you get. Open this entity when your workflow needs collection-level discovery, item retrieval, or catalog views built around grouped media.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Use these docs to work with playlist: By user identifier when your product needs a clear API method into public playlist workflows.
Open these docs when you need the actual playlist content surface for monitoring, archive jobs, or reporting workflows.
Post API methods collect public publishing activity and the objects most teams use first for monitoring and analysis.
What you get. This group is a strong fit for feed views, archive jobs, campaign reporting, and any workflow that starts from the content stream itself.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Use these docs to work with posts: By user identifier when your product needs a clear API method into public posts workflows.
Use this API method to inspect the public conversation around posts and understand how people are reacting to the content.
Start here when you need richer public context behind posts: Details by post ID and want the most complete identity view first.
Search API methods expose public discovery surfaces, queries, and intent signals across the platform.
What you get. This entity is a natural entry point for research, prospecting, alerting, and products that need to find people, content, or topics fast.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Use these docs to work with search: All by country when your product needs a clear API method into public search workflows.
Use these docs to work with search: Channels by country when your product needs a clear API method into public search workflows.
Open these docs when you need the actual search content surface for monitoring, archive jobs, or reporting workflows.
Use these docs to work with search: Movies By Country when your product needs a clear API method into public search workflows.
Open these docs when you need the actual search content surface for monitoring, archive jobs, or reporting workflows.
Use these docs to work with search: Shorts By Country when your product needs a clear API method into public search workflows.
Open these docs when you need the actual search content surface for monitoring, archive jobs, or reporting workflows.
Video API methods are designed for public video discovery, monitoring, and performance-oriented workflows.
What you get. Use this group when your product needs item-level video data, channel expansion, or reporting around supported video surfaces.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Use this API method to inspect the public conversation around videos and understand how people are reacting to the content.
Start here when you need richer public context behind videos: Details by video ID and want the most complete identity view first.
Use these docs to work with videos: Related by video ID when your product needs a clear API method into public videos workflows.
A YouTube integration typically starts with channel identity, then expands into video, playlist, comment, and search surfaces.
Use profile API methods to establish channel metadata and the identifiers your product will track.
Add videos, shorts, playlists, posts, and comments based on the analytics or monitoring surface you need.
Use search and country-aware API methods when your workflow needs topical or regional discovery.
Link every product feature back to docs URLs, API method pricing, and response structures.
Use the sample request as a working starting point, then open the full docs for parameter details.
No required query parameters for this representative API method.
curl --request GET \
--url "https://www.scrapestorm.net/api/v2/youtube.com/profile/about-by-user-identifier" \
--header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
# Optional parameters:
# --data-urlencode 'user_identifier=mkbhd'
X-API-Key
YouTube API methods share the same credit accounting model as the rest of ScrapeStorm and can be reviewed in the pricing catalog.
ScrapeStorm is not affiliated with YouTube. Process data only where you have a valid business and legal basis.
API method prices are visible before integration and credits are tied to successful API responses.
Each platform page links to the API reference and implementation docs for exact request and response details.
ScrapeStorm is independent from the listed platforms; your team remains responsible for permitted data processing.
These answers cover coverage, pricing, response formats, and launch details before you commit engineering time.
Use the version switch on this page: choose V2 for normalized ScrapeStorm fields and V1 when compatibility requires the original platform-shaped response.
Yes. Several search and feed methods expose country-aware parameters where the upstream surface supports them.
Yes. The page groups content API methods so you can evaluate shorts, videos, playlists, posts, and comments from one product surface.
No. It is designed as a product page first, with API method coverage, use cases, pricing links, and implementation docs in one flow.
Yes. Use the linked docs or API reference page for the selected YouTube method.