YouTube API

YouTube Search API

Search YouTube and get matching videos: title, channel, view count, length and publish time.

$0.50/1k req, pay per request, no subscription.

What the API returnedvideos[0]
{
"id": "BzSzwqb-OEE",
"url": "https://www.youtube.com/watch?v=BzSzwqb-OEE",
"title": "Apollo 11 Moon Landing: Restored Footage",
"channel": "NASA",
"views": 14860541,
"lengthText": "4:14",
"publishedTime": "2 years ago",
"authorAvatarUrl": string,
... 3 more fields
}
Uptime
99.99%
30d · 120,925 calls
Requests
120,943
30d · weekly, last 12 wks
Response
1.9s
median · 30d

Pricing and providers

YouTube Search API pricing: one API, 3 interchangeable providers

The cheapest provider serves first. If it fails, the next one takes over in the same call.

You pay
$5.00
$0.50/1k req, only for what you use. No monthly plan.
Your first 200 requests are free with the $0.10 starting balance.

Try it

Get YouTube search in one request

requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `nextCursor`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a result that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.

This sample shows 10 of 16 fields. See every field

{
  "found": true,
  "data": {
    "videos": [
      {
        "id": "BzSzwqb-OEE",
        "url": "https://www.youtube.com/watch?v=BzSzwqb-OEE",
        "title": "Apollo 11 Moon Landing: Restored Footage",
        "channel": "NASA",
        "views": 14860541,
        "lengthText": "4:14",
        "publishedTime": "2 years ago"
      }
    ]
  }
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-10-31 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • querystring

    apollo 11 landing

    The YouTube search query.

  • cursorstring

    Continuation token from a previous response for pagination.

  • requireCursorboolean

    Deprecated; send `requireFields: ["nextCursor"]` instead, which does exactly the same thing. Set true if you intend to page through results, so the request is only served by a source that can return a nextCursor. Omit it and routing is unchanged, with the cheapest source serving. This can raise your price: when the cheapest source cannot page, a source that can serves, and you are quoted and charged its price. It stays accepted so callers that already send it keep working.

  • requireFieldsarray

    Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `nextCursor`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a result that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.

  • sortByenum

    Sort order: "relevance" (default) or "popular" (most-viewed).

  • uploadDateenum

    Filter by upload recency. Omit for any time.

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

datadata
  • nextCursorstringcan require

    Opaque cursor for the next page of results, or null when this lane has no more. Pass it back as cursor to continue.

each videodata.videos[]

Populated whenever the provider has data for the entity.

  • authorAvatarUrlstring

    URL of the publishing channel's avatar image.

  • authorIdstring

    YouTube channel ID of the publishing channel.

  • channelstring

    NASA

    Populated whenever the provider has data for the entity.

  • createdUtcnumber

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds.

  • idstring

    BzSzwqb-OEE

    Populated whenever the provider has data for the entity.

  • imagestring

    URL of the video thumbnail image, tracking query parameters stripped.

  • lengthTextstring

    4:14

  • publishedTimestring

    2 years ago

    Populated whenever the provider has data for the entity.

  • titlestring

    Apollo 11 Moon Landing: Restored Footage

    Populated whenever the provider has data for the entity.

  • urlstring

    https://www.youtube.com/watch?v=BzSzwqb-OEE

    Populated whenever the provider has data for the entity.

  • viewsinteger

    14860541

top level
  • foundboolean

    true

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

You get back. Named, typed fields in the same shape whichever source answers.

Selling this API? See the full schema your endpoint must return.

FAQ

About the YouTube Search API

The AnyAPI YouTube Search API returns YouTube search data as normalized JSON from one POST call to /v1/run/youtube.search. Search YouTube and get matching videos: title, channel, view count, length and publish time. AnyAPI routes each request across 3 sources and falls back automatically when one fails. It costs from $0.50 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of YouTube search calls through AnyAPI succeeded, with a median response time of 1.9 seconds across 120,925 measured calls.

It costs from $0.50 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

Search YouTube and get matching videos: title, channel, view count, length and publish time. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of YouTube search calls through AnyAPI succeeded, with a median response time of 1.9 seconds across 120,925 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 200 YouTube Search calls at $0.0005 each.

AnyAPI asks the next of its 3 sources in the same request, cheapest first, so one source going down does not fail your call.

Send a POST request to https://api.getanyapi.com/v1/run/youtube.search with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.