Skip to main content

YouTube Live Data

The YouTube live endpoints cover topic discovery, channel research, video validation, and transcripts. Search is designed for bounded discovery jobs: choose filters, inspect one page, and continue with the returned cursor only when you need more candidates.

Endpoints and pricing

One credit is $0.01. API-key and OAuth requests are charged only when they succeed. See Pricing for the payment-rail rules.

Search for emerging videos

Use topic phrases or entities in q. Hashtags are accepted as ordinary query text, but phrases usually cover more of the language people use in titles and descriptions.
Search supports these controls: Video search results include channel identity, duration, view count, thumbnail, and relative and approximate publication data. Use the video endpoint when exact publication data or current likes and comments affect your ranking.

Continue to the next page

Each successful search returns next_cursor. Treat it as opaque and return it unchanged with the original query and filters.
Every continuation request is another 0.5-credit page. Set a page ceiling in scheduled jobs so a changing result set cannot create unbounded work.

Expand a topic seed

Typeahead returns current localized suggestions for a partial phrase.
Use a small set of distinct suggestions as search seeds, then deduplicate videos by video_id before scoring them.

Fetch exact video details

The response includes views, likes, comments, duration, tags, categories, channel identity, and published_at when YouTube supplies an exact timestamp.

Resolve a channel

Channel routes accept a bare handle, an @handle, a UC-prefixed channel ID, or a full channel URL.

MCP and no-code access

The six workflows are available through the Influship MCP server as search_youtube, get_youtube_typeahead, get_youtube_video, get_youtube_channel, get_youtube_video_transcript, and get_youtube_channel_transcripts. n8n and Make expose the same YouTube operations as dedicated fields and actions. Zapier users can call these REST endpoints from a Webhooks step.