YouTube Search Hashtag API
Scrape YouTube Search Hashtag data with one API call. Searches YouTube for videos under a specific hashtag. Returns matching videos with view counts, channel info, and publish dates. DATES: the upstream sends only a date derived from a relative label such as "3 weeks ago" (or none), so by default every such row is joined to the per-video lookup for its exact publish second, at no extra credit (one lookup per page); send `exact_dates=false` to keep the estimate instead, marked by `post.ext.published_precision`. ROWS ARE UNEVEN, from the upstream: a large minority carry only id, URL, title and view count. The same free per-video lookup that fixes the dates gives those rows their channel id (`post.ext.channel_id`) and channel name (`post.author.display_name`), but `post.content.duration_seconds`, `post.content.thumbnail_url`, `post.author.username` and `post.author.avatar_url` stay null on them. With `exact_dates=false` no lookup runs, so the channel stays null too. That is a property of YouTube's hashtag shelf, not of your query. Send `include=engagement` to fill the duration in the same call, and `include=engagement,channel` for the handle and avatar: every row is joined to the per-video lookup, which supplies likes, comments, the duration, the exact publish time and the channel; `include=channel` adds the channel's subscriber count. Each costs 1 credit per distinct video or channel filled, at most 5 per page. TITLES: the free per-video lookup swaps YouTube's English machine-translated listing title for the creator's own; a title not swapped carries `post.ext.title_maybe_translated: true` (`exact_dates=false` skips the lookup).
Last updated October 2026Maintained by the SocialCrawl team
Returns videos posted under a hashtag, each with view count, channel info, and publish date.
Use it to read a hashtag feed rather than a keyword query; set type to shorts to limit the results to Shorts.
Searching 68 platforms in parallel
What can you do with the Search Hashtag API?
The Search Hashtag endpoint gives you structured YouTube data with computed fields in a single request. No scraping infrastructure to build or maintain.
Example Request
curl -H "x-api-key: YOUR_API_KEY" \
"https://www.socialcrawl.dev/v1/youtube/search/hashtag?hashtag=shorts"import requests
response = requests.get(
"https://www.socialcrawl.dev/v1/youtube/search/hashtag",
params={
'hashtag': 'shorts',
},
headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()const response = await fetch(
"https://www.socialcrawl.dev/v1/youtube/search/hashtag?hashtag=shorts",
{
headers: { "x-api-key": "YOUR_API_KEY" },
},
);
const data = await response.json();Parameters
| Parameter | Required | Description |
|---|---|---|
| hashtag | Yes | Hashtag to search for without the # symbol |
| continuationToken | No | Continuation token to get more videos. Get 'continuationToken' from previous response. |
| type | No | Search for all types of content or only shorts (all | shorts) |
| include | No | Set to `engagement`, `channel`, or both (`engagement,channel`) to fill more of every row in this one call. `engagement` fills `post.engagement.views`, `.likes` and `.comments`, `post.content.duration_seconds`, `post.ext.channel_id` and `post.author.display_name` where the row lacks them, and replaces a date derived from a label such as "4 months ago" with the exact publish time (removing `post.ext.published_precision`). `channel` puts the channel's subscriber count on `post.ext.author_followers` (YouTube's own figure, which it rounds to three significant figures above 1,000) and fills the channel's `post.author.display_name`, `.avatar_url` and `.username` where missing. Send both to cover rows that arrive without a channel id: the video join supplies it and the channel join then uses it. Each join costs 1 credit per distinct video or channel it filled, and never more than 5 per 50; ids that could not be filled are refunded. Each join adds 0.2 to 0.7 seconds on a fresh page (one lookup per 50 ids, never more than 8 seconds). Read `data.hydration` for the rows, lookups, credits held and kept, and the time. |
| exact_dates | No | Exact publish dates are on by default and free. A row whose date the upstream derived from a relative label such as "4 months ago" (measured up to four months off) is joined to the per-video lookup for its exact publish second, at no extra credit: one lookup per page (two on a page past 50 rows, side by side), adding about 0.2 to 0.7 seconds (never more than 3). The same lookup swaps the listing title, often YouTube's English machine translation, for the creator's own, and `computed.language` follows it; a title not swapped carries `post.ext.title_maybe_translated: true`. Set to `false` to skip the lookup: rows then carry the supplier's date estimate (a day-granular or coarser label truncated to midnight UTC), marked by `post.ext.published_precision` and `post.ext.published_label`, and the listing title, marked by `post.ext.title_maybe_translated`. A row the lookup could not resolve keeps those values and markers, and `_warnings` carries `exact_dates_partial` (some rows) or `exact_dates_unavailable` (none); on `channel/videos`, whose dates are already exact, the warnings are `original_titles_partial` and `original_titles_unavailable`. (true | false) |
| since | No | Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following `next_cursor`, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. `published_after`, `start_date`, `from_date`, `publish_time` (`yesterday`, `this-week`, `this-month`, `last-3-months`, `last-6-months`) and `max_age_days` are accepted and applied as `since`. |
| until | No | Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. `published_before`, `end_date` and `to_date` are accepted and applied as `until`. |
| min_views | No | Keep only rows with at least this many views (`post.engagement.views`). A row whose view count is unknown is discarded, so every returned row meets the floor. Filtering runs on our side after each page is fetched, so every page walked is billed as usual; `data.walk.discarded` counts what was removed and why. |
| max_age_days | No | Keep only rows published within this many days (`post.published_at`), 1 to 3650. A row with no date is discarded. Filtering runs on our side after each page is fetched, so every page walked is billed as usual; `data.walk.discarded` counts what was removed and why. |
| sort_rows | No | `views`: return the kept rows ordered by view count, highest first, across every page walked. Rows without a view count go last. (views) |
| max_pages | No | 1 to 5 (default 1). Walk up to this many pages in one call and return the rows from all of them (after any filter). Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `time_budget`, `page_error`) and `data.next_cursor` continues from where it stopped. |
| seen | No | An id you choose (1 to 64 letters, digits, `.`, `_` or `-`). Rows your account already received under the same `seen` id are removed from the page, and the page price falls with the share of repeats: page credits x new rows / rows on the page, rounded up, so a page of nothing but repeats is free. Only the page's own price is discounted: credits for joined data (`include=`) are charged only for rows you have not received, and are never discounted. The memory lasts 24 hours from the last call that used the id, holds row ids only, and is private to your account. Use one id across a set of related searches; `data.walk.repeats` counts what was removed. |
What does the YouTube Search Hashtag API return?
Every response follows one unified schema. Here is a real, unmodified response body, so you can see the exact fields you get back before spending a credit.
Example response
{
"success": true,
"platform": "youtube",
"endpoint": "/v1/youtube/search/hashtag",
"data": {
"items": [
{
"post": {
"id": "Li8RTsmujBI",
"url": "https://www.youtube.com/watch?v=Li8RTsmujBI",
"content": {
"text": "Sample comment text (redacted).",
"media_urls": null,
"thumbnail_url": "https://i.ytimg.com/vi/Li8RTsmujBI/hq720.jpg?sqp=-oaymwErCNAFEJQDSFryq4qpAx0IARUAAIhCGAHYAQHiAQoIGBACGAY4AUABuAL3GA==&rs=AOn4CLAtU4QpB8L6RlwTnheFEqt3JexR6w",
"duration_seconds": 219
},
"author": {
"username": "user_75fd8b",
"display_name": "user_9b4984",
"avatar_url": "https://example.com/avatars/user_c06a0b.png",
"verified": null
},
"engagement": {
"views": 8557,
"likes": null,
"comments": null,
"shares": null,
"saves": null
},
"flags": {
"nsfw": null,
"spoiler": null,
"pinned": null,
"deleted": false
},
"published_at": "2026-10-01T21:10:05.000Z",
"ext": {
"content_type": "video",
"description": null,
"channel_id": "UC6ZFN9Tx6xh-skXCuRHCDpQ",
"published_label": "10 hours ago"
}
},
"computed": {
"engagement_rate": null,
"language": "en",
"content_category": "other",
"estimated_reach": 10268
}
},
{
"post": {
"id": "tE5qHBUDYjg",
"url": "https://www.youtube.com/watch?v=tE5qHBUDYjg",
"content": {
"text": "Sample comment text (redacted).",
"media_urls": null,
"thumbnail_url": null,
"duration_seconds": null
},
"author": {
"username": null,
"display_name": "user_2a3642",
"avatar_url": null,
"verified": null
},
"engagement": {
"views": 3200,
"likes": null,
"comments": null,
"shares": null,
"saves": null
},
"flags": {
"nsfw": null,
"spoiler": null,
"pinned": null,
"deleted": false
},
"published_at": "2026-10-01T23:00:10.000Z",
"ext": {
"content_type": "short",
"description": null,
"channel_id": "UC2eNsx687ZQF0jQu0U8uaDA"
}
},
"computed": {
"engagement_rate": null,
"language": "en",
"content_category": "other",
"estimated_reach": 3840
}
}
],
"next_cursor": "sc1.eyJjIjoiRWo0U0NTSWpjMmh2Y25Seklob3VVMEpUUTBGUmRFMWhWR2hUVmtoT2RHUlhjRU5UWWtsQ1FtZHZSVU5CVFZGQmRXOUNRa0ZuUTBWQ2F5VXpSS0FDQkJpQjRPZ1lJZ3R6WldGeVkyZ3RabVZsWkElM0QlM0QiLCJzIjpbIkxpOFJUc211akJJIiwidEU1cUhCVURZamciLCJKMjJvSWNHSWtQOCIsIk1UamhlU1ZGa3FZIiwiRVBvVElFT2xnM1EiLCJmRnlIbUh0TTJLayIsInFpWE1tLW5QNmJzIiwibkVIWVZBb2g3LUEiLCJ6d2hjRDdHbThBZyIsIkl0WGtSdE5Gam1vIiwiemxHeGQ5cEt5WmMiLCJrVTBDanVVVlFEdyIsImpQYUJwYnhobDNnIiwiVWhuMllzSkRnUUkiLCJVRTZKLVhHNkk0TSIsIjR4cXRZa3JzQmVnIiwiNWJVelpVN29zdUkiLCJpbXhvUy1DZUl3NCIsImk2V05kNkZ1QzZFIiwiek9FMFhuQTY1RkEiLCJOVTAtZ0NKR19xQSIsImhBZFRncVcxZlB3IiwiWEQybGdrU1k0MjgiLCJIZ2tObUNXbjFqNCIsInF4aXA2eUNWd3lzIiwiREUweGtnZDlPMkEiXX0",
"total": null,
"dropped": 0
},
"credits_used": 1,
"request_id": "req_example000000",
"cached": false,
"pagination": {
"next_cursor": "sc.eyJ2IjoyLCJjIjoic2MxLmV5SmpJam9pUldvMFUwTlRTV3BqTW1oMlkyNVNla2xvYjNWVk1FcFVVVEJHVW1SRk1XaFdSMmhVVm10b1QyUkhVbGhqUlU1VVdXdHNRMUZ0WkhaU1ZVNUNWRlpHUW1SWE9VTlJhMFp1VVRCV1EyRjVWWHBTUzBGRFFrSnBRalJQWjFsSlozUjZXbGRHZVZreVozUmFiVlpzV2tFbE0wUWxNMFFpTENKeklqcGJJa3hwT0ZKVWMyMTFha0pKSWl3aWRFVTFjVWhDVlVSWmFtY2lMQ0pLTWpKdlNXTkhTV3RRT0NJc0lrMVVhbWhsVTFaR2EzRlpJaXdpUlZCdlZFbEZUMnhuTTFFaUxDSm1SbmxJYlVoMFRUSkxheUlzSW5GcFdFMXRMVzVRTm1Keklpd2lia1ZJV1ZaQmIyZzNMVUVpTENKNmQyaGpSRGRIYlRoQlp5SXNJa2wwV0d0U2RFNUdhbTF2SWl3aWVteEhlR1E1Y0V0NVdtTWlMQ0pyVlRCRGFuVlZWbEZFZHlJc0ltcFFZVUp3WW5ob2JETm5JaXdpVldodU1sbHpTa1JuVVVraUxDSlZSVFpLTFZoSE5razBUU0lzSWpSNGNYUlphM0p6UW1Wbklpd2lOV0pWZWxwVk4yOXpkVWtpTENKcGJYaHZVeTFEWlVsM05DSXNJbWsyVjA1a05rWjFRelpGSWl3aWVrOUZNRmh1UVRZMVJrRWlMQ0pPVlRBdFowTktSMTl4UVNJc0ltaEJaRlJuY1ZjeFpsQjNJaXdpV0VReWJHZHJVMWswTWpnaUxDSklaMnRPYlVOWGJqRnFOQ0lzSW5GNGFYQTJlVU5XZDNseklpd2lSRVV3ZUd0blpEbFBNa0VpWFgwIiwiZSI6InlvdXR1YmUvc2VhcmNoL2hhc2h0YWciLCJwIjoiY29udGludWF0aW9uVG9rZW4ifQ",
"has_more": true,
"page_size": 26
},
"credits_remaining": 9999,
"source": "captured",
"captured_at": "2026-10-02T07:30:03.232Z",
"redacted": true
}Live sample illustrating the unified response shape. Field values reflect the record you query.
How does the YouTube Search Hashtag API work?
Send a GET request with your API key and get back clean, structured JSON in our unified schema. Supported computed fields are populated when the source provides the required inputs.
Method
GET
Response
JSON
How do you scrape social media data in seconds?
The fastest social media scraping API for developers. Scrape profiles, posts, comments, and analytics from 68 platforms covering 10B+ monthly active users.
One schema, every platform
Query 68 platforms with identical response structures. Write your integration once.
Computed fields, not just scraped
When an endpoint supports these metrics and the source provides the required inputs, the normalized record includes engagement_rate, estimated_reach, content_category, and language. Ready to use.
See your data before you code
Visual Data Explorer. Paste any URL, get rich result cards, sortable tables, CSV export.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usHow do I search YouTube by hashtag?
Can I restrict hashtag results to Shorts only?
How is this different from keyword search?
How do I paginate through hashtag results?
Is this good for tracking a marketing hashtag?
Ask AI about SocialCrawl
Ready to scrape YouTube Search Hashtag data?
Get your API key and start pulling YouTube data in under 60 seconds.
