Quick Start
Request
Response
Specification
Endpoint
GET https://api.supadata.ai/v1/youtube/search
Each request requires an x-api-key
header with your API key available after signing up. Get your API key here.
Query Parameters
Parameter | Type | Required | Description |
---|---|---|---|
query | string | Yes | Search query string |
type | string | No | Filter by content type. Options: all (default), video , channel , playlist , movie |
uploadDate | string | No | Filter by upload date. Options: all (default), hour , today , week , month , year |
duration | string | No | Filter by video duration. Options: all (default), short (<4min), medium (4-20min), long (>20min) |
sortBy | string | No | Sort order of results. Options: relevance (default), rating , date , views |
features | array | No | Array of special features to filter by. Options: hd , subtitles , creative-commons , 3d , live , 4k , 360 , location , hdr , vr180 |
limit | number | No | Maximum number of results to return (1-5000). When provided, API automatically paginates to fetch up to this many results |
nextPageToken | string | No | Token for fetching the next page of results. When provided, other filter parameters are ignored |
Pagination
The search endpoint supports two different pagination modes depending on whether you use thelimit
parameter.
Supadata SDKs automatically handle pagination for you. Please use the API if
you need to control pagination.
Automatic Pagination (with limit
)
When you provide a limit
parameter, the API automatically handles pagination for you:
- The API fetches multiple pages behind the scenes until it reaches your desired
limit
or runs out of results - You receive all results in a single response
- Each page fetched counts as 1 credit (so requesting 100 results might consume 5+ credits if each page contains ~20 results)
- No
nextPageToken
is returned since all requested results are included
- You need a specific number of results
- You want convenience over credit control
- You’re building bulk data collection tools
Manual Pagination (without limit
)
When you don’t provide a limit
parameter, you get manual control over pagination:
- You receive one page of results (~20 items) per request
- Each request consumes exactly 1 credit
- A
nextPageToken
is included in the response for fetching additional pages - When using
nextPageToken
, all other filter parameters are ignored
- You want precise credit control
- You’re implementing infinite scroll or “Load More” functionality
- You only need the first page of results
- You’re building interactive applications where users control pagination
Error Codes
The API returns HTTP status codes and error codes. See this page for more details.Pricing
- 1 search request = 1 credit per page of results
- Using the
limit
parameter to fetch multiple pages automatically will consume credits for each page retrieved