YouTube Channel About, Playlists & Posts Finder: MCP config, n8n workflow and API
Channel profile rows with About details, external links, and optional nested surfaces, plus one-row-per-playlist and one-row-per-Community-Post modes.
Fastest route, in Claude Code:
claude mcp add --transport http youtube-channel-about-playlists-and-posts-finder "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder" One click, signs in with Apify on first use:
Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):
npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder" --name youtube-channel-about-playlists-and-posts-finder Every file on this page is generated from the Actor's published schema: 51 of 51 checks pass (validated, not run)
- MCP configs: 7 of 7 (Uses Apify's hosted MCP endpoint over HTTPS; The tools parameter lists exactly the chosen Actors as owner/name; JSON configs parse and use the client's top-level key and the same URL; Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var; CLI commands quote the same URL and use the streamable HTTP transport; One-click install links decode back to the same URL and carry no token; Only placeholders, no real token)
- n8n workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
- long-run workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
- example input: 5 of 5 (All 1 required input field is present; Every input key exists in the published input schema; Every value has the type the schema declares; Every choice field uses one of its published options; Numbers respect the published minimum and maximum)
- code snippets: 4 of 4 (curl calls the documented run-sync-get-dataset-items endpoint for this Actor; Python (apify-client 3.x typed Run) and JavaScript use the official apify-client call() then read the run's dataset; Multi-line shell commands continue every line with a backslash; Token read from APIFY_TOKEN, none embedded)
- SKILL.md: 13 of 13 (SKILL.md starts with YAML front matter; name is 1-64 lowercase letters, digits and single hyphens; name matches the skill folder name; description is present, at most 1024 characters and has no angle brackets; front matter uses only spec fields; compatibility is at most 500 characters; body has instructions; field descriptions end on whole sentences; no credential values are embedded; the token is read from APIFY_TOKEN; the run command calls this Actor's run-sync endpoint; the example input is valid JSON; the example input matches the published input schema)
What a run costs
Every run pays a start fee plus a price per result. On the Free plan this Actor's start fee is $0.40 (the start event, $0.10 per GB, times its default 4 GB of memory), $0.12 on Business; results cost $0.99 per 1,000 results (pay per event). Checked 2026-11-12.
| Results in one run | Start | Results | Run total |
|---|---|---|---|
| 10 | $0.40 | $0.010 | $0.41 |
| 100 | $0.40 | $0.10 | $0.50 |
| 1,000 | $0.40 | $0.99 | $1.39 |
Plus Apify platform usage for the run, which the caller pays. A smaller memory setting lowers the start fee if the Actor still finishes. Prices can change; the Store pricing tab is the source of truth.
MCP config
One URL works in every client: https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder. It exposes this Actor as a tool, plus fetch-actor-details so the agent can read the input schema before calling it. Pick your client:
Claude Code configterminal or .mcp.json
claude mcp add --transport http youtube-channel-about-playlists-and-posts-finder "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder" Run the command in your project folder. Add --scope user to make it available in every project. Full Claude Code setup
Claude Desktop configclaude_desktop_config.json
{
"mcpServers": {
"youtube-channel-about-playlists-and-posts-finder": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--tools",
"fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder"
],
"env": {
"APIFY_TOKEN": "YOUR_APIFY_TOKEN"
}
}
}
} Easiest: open Customize, then Connectors, choose Add custom connector, paste the server URL (the ChatGPT tab shows it on its own) and sign in to Apify. Full Claude Desktop setup
Cursor config~/.cursor/mcp.json
{
"mcpServers": {
"youtube-channel-about-playlists-and-posts-finder": {
"url": "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder",
"headers": {
"Authorization": "Bearer ${env:APIFY_TOKEN}"
}
}
}
} Save as ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one project. Merge with servers you already have. Full Cursor setup
VS Code config.vscode/mcp.json
{
"inputs": [
{
"type": "promptString",
"id": "apify-token",
"description": "Apify API token",
"password": true
}
],
"servers": {
"youtube-channel-about-playlists-and-posts-finder": {
"type": "http",
"url": "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder",
"headers": {
"Authorization": "Bearer ${input:apify-token}"
}
}
}
} Save as .vscode/mcp.json in your workspace. Full VS Code setup
ChatGPT configPlugins > Add custom MCP server
https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder In ChatGPT on the web, open Plugins, select + and choose Add custom MCP server. Full ChatGPT setup
Codex CLI config~/.codex/config.toml
[mcp_servers.youtube-channel-about-playlists-and-posts-finder]
url = "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder"
bearer_token_env_var = "APIFY_TOKEN" Add the block to ~/.codex/config.toml, or .codex/config.toml in a project. Full Codex CLI setup
Gemini CLI configterminal (writes ~/.gemini/settings.json)
gemini mcp add -t http -s user -H "Authorization: Bearer $APIFY_TOKEN" youtube-channel-about-playlists-and-posts-finder "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder" Export APIFY_TOKEN first: the shell expands it and Gemini CLI saves the header, token included, in plain text in ~/.gemini/settings.json (keep that file private). In PowerShell write $env:APIFY_TOKEN instead of $APIFY_TOKEN. Drop -s user to save it in the project's .gemini/settings.json. Full Gemini CLI setup
n8n AI Agent configMCP Client Tool node
https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder Add an AI Agent node, then attach an MCP Client Tool node to its tool input. Full n8n AI Agent setup
Tools your agent gets
Listed by Apify's MCP server 0.21.5 for this exact URL on 2026-11-11 (a tools/list call; nothing was run).
fetch-actor-detailsreads the input schemaget-actor-runchecks a run's statusget-dataset-itemsreads a run's resultsget-key-value-store-recordreads a stored record such as a file or summaryabort-actor-runstops a run that is still goingdataspryva--youtube-channel-about-playlists-and-posts-finderruns the Actor and returns its results
n8n workflow
A manual and a daily trigger call the Actor through the HTTP Request node with your Apify token, then hand each record to the destination you pick. The Actor input sits in the request body, already filled with the example below.
- Run by hand
- Every day
- Run Apify Actor
n8n workflowyoutube-channel-about-playlists-and-posts-finder.n8n.json
{
"name": "YouTube Channel About, Playlists & Posts Finder to n8n only",
"nodes": [
{
"id": "b0b31d26-cb66-4d5b-aa79-f6d66a10ea9b",
"name": "Run by hand",
"type": "n8n-nodes-base.manualTrigger",
"typeVersion": 1,
"position": [
0,
0
],
"parameters": {}
},
{
"id": "b23c44e6-5a80-40b1-aaf9-80b86528a0a3",
"name": "Every day",
"type": "n8n-nodes-base.scheduleTrigger",
"typeVersion": 1.2,
"position": [
0,
200
],
"parameters": {
"rule": {
"interval": [
{
"triggerAtHour": 8
}
]
}
},
"notes": "Activate the workflow to run on this schedule."
},
{
"id": "7c858112-1091-431e-ad87-90a79d194d67",
"name": "Run Apify Actor",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [
260,
100
],
"parameters": {
"method": "POST",
"url": "https://api.apify.com/v2/actors/dataspryva~youtube-channel-about-playlists-and-posts-finder/run-sync-get-dataset-items",
"authentication": "genericCredentialType",
"genericAuthType": "httpHeaderAuth",
"sendBody": true,
"specifyBody": "json",
"jsonBody": "{\n \"mode\": \"profiles\",\n \"channelUrls\": [\n \"https://www.youtube.com/@Apify\"\n ],\n \"includeLinks\": true,\n \"includePlaylists\": false,\n \"maxPlaylists\": 10,\n \"includePosts\": false,\n \"maxPosts\": 10,\n \"includePostDetails\": false,\n \"includePostComments\": false,\n \"maxPostComments\": 10\n}",
"options": {
"timeout": 310000
}
},
"notes": "Actor: dataspryva/youtube-channel-about-playlists-and-posts-finder. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
"notesInFlow": false
},
{
"id": "a8139f26-d2cd-423d-aaaa-76e0d2fdf42b",
"name": "Setup",
"type": "n8n-nodes-base.stickyNote",
"typeVersion": 1,
"position": [
0,
-370
],
"parameters": {
"content": "## YouTube Channel About, Playlists & Posts Finder\n\nSource: [dataspryva/youtube-channel-about-playlists-and-posts-finder](https://apify.com/dataspryva/youtube-channel-about-playlists-and-posts-finder) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Click **Execute workflow**. Each record arrives as one n8n item.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
"height": 340,
"width": 460,
"color": 6
}
}
],
"connections": {
"Run by hand": {
"main": [
[
{
"node": "Run Apify Actor",
"type": "main",
"index": 0
}
]
]
},
"Every day": {
"main": [
[
{
"node": "Run Apify Actor",
"type": "main",
"index": 0
}
]
]
}
},
"pinData": {},
"active": false,
"settings": {
"executionOrder": "v1"
},
"meta": {
"templateCredsSetupCompleted": false
},
"tags": []
} Import with Workflows, Import from file, or paste into the canvas. Credentials are not included: you select them after import.
All 7 destination variants pass the same checks at build time. Built-in nodes only, at versions n8n has shipped since 1.80: they import on n8n Cloud and older self-hosted instances without community nodes. Prefer Apify's own node? The verified community node @apify/n8n-nodes-apify runs the same Actor with OAuth sign-in on n8n Cloud.
Runs longer than 5 minutes? The synchronous endpoint answers HTTP 408 after 300 seconds. The long-run variant starts the run, checks it every minute until it ends, then reads its dataset (HTTP Request, If and Stop and Error nodes only).
Download the long-run workflow11 of 11 checks pass, not executed
Call it from code
Run the Actor from a script or your own agent framework with the Apify API. The call waits for the run to finish and returns the records. The input is the example below.
curl
curl -X POST "https://api.apify.com/v2/actors/dataspryva~youtube-channel-about-playlists-and-posts-finder/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"mode":"profiles","channelUrls":["https://www.youtube.com/@Apify"],"includeLinks":true,"includePlaylists":false,"maxPlaylists":10,"includePosts":false,"maxPosts":10,"includePostDetails":false,"includePostComments":false,"maxPostComments":10}' Install: pip install "apify-client>=3"
Python
import os
from apify_client import ApifyClient
client = ApifyClient(os.environ["APIFY_TOKEN"])
run_input = {
"mode": "profiles",
"channelUrls": [
"https://www.youtube.com/@Apify",
],
"includeLinks": True,
"includePlaylists": False,
"maxPlaylists": 10,
"includePosts": False,
"maxPosts": 10,
"includePostDetails": False,
"includePostComments": False,
"maxPostComments": 10,
}
run = client.actor("dataspryva/youtube-channel-about-playlists-and-posts-finder").call(run_input=run_input)
if run is None:
raise RuntimeError("The Actor run could not be started")
print(run.status, "dataset", run.default_dataset_id)
for item in client.dataset(run.default_dataset_id).iterate_items():
print(item) Install: npm install apify-client
JavaScript
import { ApifyClient } from "apify-client";
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const input = {
"mode": "profiles",
"channelUrls": [
"https://www.youtube.com/@Apify"
],
"includeLinks": true,
"includePlaylists": false,
"maxPlaylists": 10,
"includePosts": false,
"maxPosts": 10,
"includePostDetails": false,
"includePostComments": false,
"maxPostComments": 10
};
const run = await client.actor("dataspryva/youtube-channel-about-playlists-and-posts-finder").call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.length, items[0]); Example input
These values come from the Actor's Store prefill and required defaults. Change the search, URL or limit before your first run.
Actor inputinput.json
{
"mode": "profiles",
"channelUrls": [
"https://www.youtube.com/@Apify"
],
"includeLinks": true,
"includePlaylists": false,
"maxPlaylists": 10,
"includePosts": false,
"maxPosts": 10,
"includePostDetails": false,
"includePostComments": false,
"maxPostComments": 10
} | Field | Type | What it does |
|---|---|---|
mode | string (3 options) | Channel profile returns one row per channel with its About details. Playlists returns one row per public playlist, show, course, or podcast. Posts returns one row per public Community Post. |
channelUrls required | array | Public YouTube channel URLs, @handles, or UC… channel IDs. One row set is produced for each channel. |
includeLinks | boolean | In channel profile mode, include the external links shown on the public About page, with their titles and favicons. |
includePlaylists | boolean | In channel profile mode, add a snapshot of the channel's public playlists, shows, courses, and podcasts to the same row. Use the playlists mode for one row per playlist. |
maxPlaylists | integer | Maximum playlist, show, course, or podcast rows to collect per channel. Applies to the playlists mode and to nested profile snapshots. |
includePosts | boolean | In channel profile mode, add a snapshot of the channel's public Community Posts to the same row. Use the posts mode for one row per post. |
maxPosts | integer | Maximum Community Posts to collect per channel. Applies to the posts mode and to nested profile snapshots. YouTube exposes at most 200 posts per channel. |
includePostDetails | boolean | Open each Community Post's public detail page to fill its exact ISO publish date and exact like count. Adds one request per post. |
includePostComments | boolean | Collect public comments on each Community Post, up to the per-post limit. Adds one detail and one or more comment requests per post. |
maxPostComments | integer | Maximum public top-level comments to keep per Community Post when comments are included. Replies are not expanded. |
What your agent receives
Each run returns a list of records. The Actor publishes 20 fields, starting with channelName, title, handle, subscriberCountText.
| Field | What it holds | Format |
|---|---|---|
recordType | Type | text |
channelName | Channel | text |
title | Title | text |
handle | Handle | text |
subscriberCountText | Subscribers | text |
videoCountText | Videos | text |
totalViewsText | Total views | text |
country | Country | text |
joinedDateText | Joined | text |
isVerified | Verified | boolean |
10 more fields
| Field | What it holds | Format |
|---|---|---|
playlistType | Type | text |
videoCount | Items | number |
lastUpdatedText | Updated | text |
playlistUrl | URL | link |
postType | Type | text |
postId | ||
publishedAt | Published | text |
likeCount | Likes | number |
contentText | Text | text |
postUrl | URL | link |
Agent skill
A SKILL.md in the open Agent Skills format. It teaches Claude Code, Codex and other skill-aware agents when to call this Actor, how to build the input and how to read the result, using the API directly.
SKILL.mdyoutube-channel-about-playlists-and-posts-finder/SKILL.md
---
name: youtube-channel-about-playlists-and-posts-finder
description: "Channel profile rows with About details, external links, and optional nested surfaces, plus one-row-per-playlist and one-row-per-Community-Post modes. Runs the Apify Actor dataspryva/youtube-channel-about-playlists-and-posts-finder. Use when the user needs YouTube data with fields such as recordType, channelName, title, handle, subscriberCountText, videoCountText and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
actor: "dataspryva/youtube-channel-about-playlists-and-posts-finder"
store-url: "https://apify.com/dataspryva/youtube-channel-about-playlists-and-posts-finder"
---
# YouTube Channel About, Playlists & Posts Finder
Use this skill to fetch YouTube data with the Apify Actor `dataspryva/youtube-channel-about-playlists-and-posts-finder` and work with the returned rows.
## Before running
1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.
## Input fields
| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `profiles`, `playlists`, `posts` | Channel profile returns one row per channel with its About details. Playlists returns one row per public playlist, show, course, or podcast. Posts returns one row per public Community Post. |
| `channelUrls` | array, required | Public YouTube channel URLs, @handles, or UC… channel IDs. One row set is produced for each channel. |
| `includeLinks` | boolean | In channel profile mode, include the external links shown on the public About page, with their titles and favicons. |
| `includePlaylists` | boolean | In channel profile mode, add a snapshot of the channel's public playlists, shows, courses, and podcasts to the same row. Use the playlists mode for one row per playlist. |
| `maxPlaylists` | integer | Maximum playlist, show, course, or podcast rows to collect per channel. Applies to the playlists mode and to nested profile snapshots. |
| `includePosts` | boolean | In channel profile mode, add a snapshot of the channel's public Community Posts to the same row. Use the posts mode for one row per post. |
| `maxPosts` | integer | Maximum Community Posts to collect per channel. Applies to the posts mode and to nested profile snapshots. YouTube exposes at most 200 posts per channel. |
| `includePostDetails` | boolean | Open each Community Post's public detail page to fill its exact ISO publish date and exact like count. Adds one request per post. |
| `includePostComments` | boolean | Collect public comments on each Community Post, up to the per-post limit. Adds one detail and one or more comment requests per post. |
| `maxPostComments` | integer | Maximum public top-level comments to keep per Community Post when comments are included. Replies are not expanded. |
Example `input.json` (the Actor's published prefill):
```json
{
"mode": "profiles",
"channelUrls": [
"https://www.youtube.com/@Apify"
],
"includeLinks": true,
"includePlaylists": false,
"maxPlaylists": 10,
"includePosts": false,
"maxPosts": 10,
"includePostDetails": false,
"includePostComments": false,
"maxPostComments": 10
}
```
## Run
```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~youtube-channel-about-playlists-and-posts-finder/run-sync-get-dataset-items" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d @input.json > results.json
```
The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/dataspryva~youtube-channel-about-playlists-and-posts-finder/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.
## Output
Each item is one record. Published fields include: `recordType`, `channelName`, `title`, `handle`, `subscriberCountText`, `videoCountText`, `totalViewsText`, `country`, `joinedDateText`, `isVerified`, `playlistType`, `videoCount`, `lastUpdatedText`, `playlistUrl`, `postType`, `postId`, `publishedAt`, `likeCount`, `contentText`, `postUrl`.
Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.
- Claude Code: save it as
~/.claude/skills/youtube-channel-about-playlists-and-posts-finder/SKILL.md, or.claude/skills/youtube-channel-about-playlists-and-posts-finder/SKILL.mdin a project. - Codex and other agents:
~/.agents/skills/youtube-channel-about-playlists-and-posts-finder/SKILL.md, or.agents/skills/youtube-channel-about-playlists-and-posts-finder/in a project. - Or let the skills CLI place it for your agent:
npx skills add https://recipeforagents.com --skill youtube-channel-about-playlists-and-posts-finder - Set
APIFY_TOKENin the agent's environment.
Troubleshooting
Why does the client say Unauthorized or invalid token?
Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.
Source: Apify MCP server README
Why did my agent's tool list change after an update?
Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.
Source: Apify MCP server README
What happens when the agent sends input the Actor rejects?
The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.
Source: Apify MCP server README
Questions
How do I connect YouTube Channel About, Playlists & Posts Finder to Claude?
In Claude Code run: claude mcp add --transport http youtube-channel-about-playlists-and-posts-finder "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder". In Claude Desktop or claude.ai add a custom connector with the URL https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/youtube-channel-about-playlists-and-posts-finder and sign in to Apify. The agent then gets one tool for this Actor plus a tool that reads its input schema.
What input does YouTube Channel About, Playlists & Posts Finder need?
The published input schema requires channelUrls. The example on this page uses the Actor's own Store prefill.
What does YouTube Channel About, Playlists & Posts Finder cost to run?
The Apify Store lists $0.99 per 1,000 results (pay per event) for this Actor, checked 2026-11-12. Runs are billed to the Apify account whose token or sign-in the agent uses; Apify platform usage can add to that.
Which tools does the MCP config give my agent?
6 tools: fetch-actor-details, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run, dataspryva--youtube-channel-about-playlists-and-posts-finder. Apify's MCP server listed them for this exact URL on 2026-11-11.
More YouTube Actors
YouTube Channel Video Catalog & Profile Scraper
Get a YouTube channel's profile details (subscribers, description, links, verification) together with its…
49 fields$0.99 per 1,000 resultsYouTube Channel Video Feed Quick Scraper
Quickly list any YouTube channel's videos, sorted newest, most popular or oldest, with channel subscriber…
52 fields$0.99 per 1,000 resultsYouTube Community Tab Post & Poll Scraper
Read a YouTube channel's Community tab and get structured records for every text post, image, poll, and…
7 fields$0.99 per 1,000 resultsYouTube Hashtag Video & Shorts Ranking Scraper
Look up one or more YouTube hashtags and get the videos and Shorts currently ranked under them, in order…
40 fields$0.99 per 1,000 resultsYouTube Live Stream & Replay Chat Extractor
Collect chat messages, Super Chats, Super Stickers, and membership events from an active YouTube livestream…
15 fields$0.99 per 1,000 resultsYouTube Playlist Contents & Channel Playlist Finder
List every video in a YouTube playlist, or discover every public playlist a channel owns, with titles…
47 fields$0.99 per 1,000 results