YouTube · Search and trends

YouTube Trending Shorts Scraper API

The YouTube Trending Shorts endpoint is one API call: send a single call with no required parameters with your HProxy key and get back a clean, structured JSON object. Pull the Shorts trending on YouTube right now, recomputed live on every call, with view counts and the channel behind each. HProxy runs the proxies, sessions, anti-bot handling and parsing server-side, so there is no headless browser to babysit and no parser to keep fixing when YouTube changes its markup. You only ever touch the JSON.
  • 0.15¢ per call
  • $1.49 per 1,000
  • Takes a single call with no required parameters
  • Errors and timeouts are not charged

The call

One GET, and the trending shorts comes back as JSON.

Your key goes in one header. The answer is the object below it.

The full reference
curl "https://hproxy.com/api/v1/scrape/youtube/trending-shorts" \
  -H "X-API-Key: hpx_your_key_here"
Response200 OK · JSON
{
  "region": "US",
  "items": [
    { "rank": 1, "change": 4, "title": "the sound everyone is using", "id": "72901..." }
  ]
}

What comes back

The YouTube trending shorts object.

items[]
The ranked trend feed as the platform orders it.
rank / change
Current position and movement since the last window.
region
The market the ranking was computed for.

What it takes

Parameters.

How it works

Scraping YouTube trending shorts, in three steps.

You write one line. Proxies, anti-bot walls, rendering and parsing happen on our side.

  1. 1

    Create a free account

    Sign up and top up any amount. The balance pays for every HProxy product.
  2. 2

    Grab your API key

    One key from the dashboard authenticates every scraper.
  3. 3

    Call the endpoint

    Send the GET you need and read the JSON. That is the entire integration.

What people build with it

Where the YouTube trending shorts endpoint earns its keep.

  • Catch a trend on YouTube while it is still climbing.
  • Feed a trend dashboard that refreshes on every call.
  • Compare what is trending across regions.

YouTube trending shorts questions

Answered before you ask.

The reference

Send one authenticated HTTPS request to the YouTube Trending Shorts endpoint with a single call with no required parameters and your HProxy API key. Pull the Shorts trending on YouTube right now, recomputed live on every call, with view counts and the channel behind each. No proxies, no headless browser and no parsing on your side. The response is ready-to-use JSON.

This endpoint is 0.15¢ per successful call, which is $1.49 per 1,000. It bills from your HProxy balance with no subscription and no monthly minimum. Errors are retried and never charged; a lookup whose target does not exist counts as a call.

The API only accesses publicly available YouTube data, the same pages anyone can open in a browser. You are responsible for using the data in line with applicable laws and YouTube's terms for your use case.

A structured JSON object with the full trending shorts data YouTube exposes publicly. See the fields listed above. The schema is consistent across calls, so you integrate once and rely on it.

No. Every call runs on HProxy's own residential network behind the scenes, so requests look like real users. The proxy layer is already included in the per-call price.

More on the YouTube Trending Shorts API

What the YouTube Trending Shorts endpoint returns

Pull the Shorts trending on YouTube right now, recomputed live on every call, with view counts and the channel behind each. The JSON object carries items[], rank / change and region. Nothing is summarised away on our side, so what you read in the response is what the YouTube trending shorts page itself holds.

What you send to the YouTube Trending Shorts API

The call takes a single call with no required parameters. Your key travels in the X-API-Key header, the response is JSON, and the call is billed at 0.15¢, $1.49 per 1,000.

Search and trends on other platforms

The same search and trends data is available on 6 other platforms: TikTok Trending Feed, Instagram Reels Search, Reddit Search, Threads Search, Google Search Results and Pinterest Search. They share this endpoint's JSON shape, its per-call billing and your one API key, so moving from YouTube to another network is a change of URL rather than a second integration.

Is scraping YouTube trending shorts allowed?

The endpoint reads publicly available YouTube data, the same pages anyone can open in a browser without logging in. It does not touch private accounts or anything behind a password. How you then use the data is yours to keep lawful, under the rules that apply to you and to YouTube.

Ready when you are.

Your dashboard is ten seconds away. No sales call, no subscription, no minimum.