> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/twitter/hashtags>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/twitter/hashtags.mdx>

---

# X (Twitter) Hashtag Search API

Tag-led discovery on X — hashtag in, structured tweet (and people) rows out, same envelope as the rest of the Twitter tag.

`GET /v1/twitter/hashtags` takes a required `hashtag` query param and returns matching public posts in the shared Social Fetch envelope. Optional `section` (`top`, `latest`, `people`, `photos`, `videos`) picks the feed style; omit it for the default `top` feed. Optional `limit` is a best-effort page size (1–20); the actual page size may differ. When `data.page.hasMore` is true, pass `data.page.nextCursor` as `cursor` on the next call. Read `data.tweets` for post rows and `data.people` when the people section returns profiles. Bill from `meta.creditsCharged`.

This route is hashtag-focused discovery. Free-text keyword search is `GET /v1/twitter/search`. Profile cards are `GET /v1/twitter/profiles/{handle}`. All sit on one Social Fetch API key — no X developer app required for these public lookups.

## Request

- **Endpoint:** `GET /v1/twitter/hashtags`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by hashtag
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/twitter/hashtags/get)
- **Platform page:** [/platforms/twitter](https://www.socialfetch.dev/platforms/twitter)

## FAQ

### What does the X / Twitter Hashtag Search API return?

A page of public posts under data.tweets for the requested hashtag, plus data.people when the people section returns profiles, and pagination under data.page (hasMore, nextCursor). Each response uses the shared Social Fetch envelope with meta.requestId and meta.creditsCharged.

### How do I call Twitter hashtag search?

Send GET /v1/twitter/hashtags with x-api-key and a required hashtag parameter. Optionally add section (top, latest, people, photos, videos), limit (1–20, best-effort; the actual page size may differ), and cursor. See the API docs for parameters and examples.

### How much does Twitter hashtag search cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth. Each paginated page is a separate billed request.

### Is this the same as Twitter keyword search?

No. GET /v1/twitter/hashtags is hashtag-focused discovery. Free-text keyword search (operators, quotes, date and engagement floors) is GET /v1/twitter/search. Use the Twitter hub docs if your job needs both.

### What is the difference between section=latest and section=top?

section picks the hashtag feed style. Use latest for frequent polls and crisis watches; use top for recap-style dashboards. Other values include people, photos, and videos. Omit section to use the default top feed.

### How does pagination work on Twitter hashtag search?

When data.page.hasMore is true, pass data.page.nextCursor as the cursor query param on the next request. Keep the same hashtag and section across pages. The cursor is opaque.

### Do I need an X developer app or Bearer token?

No. You authenticate to Social Fetch with an API key. The route reads public hashtag results; it does not act on behalf of a logged-in X user or require elevated X API access.