Introducing the Instagram APIRead more →

X (Twitter) Post Search API. Posts matching your search.

Posts by keyword, hashtag or @mention. We handle the proxies, blocks and platform changes.

X (Twitter) Post Search API at a glance

Returns the X (Twitter) posts a web search finds for your words, a #hashtag or an @handle, each with its link, author and exact publish time. The text and the author's name are the search index's copy. Add fill=true to get each post's full record from X in the same response: full text, media, views, likes, reposts, replies and the author's verification. Filter by date with since and until, and page through results with the cursor.

GET /v1/x/search_posts

Read the API reference
  • 1 credit per page, +1 per result filled in, up to 51 credits, $0.75–$1.97 per 1,000 pages
  • 16 typed fields null when unknown
  • 50 posts per page, the search engine's ranking (most relevant first)
  • query is all it needs, e.g. coffee roaster

Send one request. Get up to 50 posts back.

Copy the request in your language, or hand it to your agent. Sign up for an API key and your first 100 credits are free.

$ npm install socialtap
query = coffee roaster
GET /v1/x/search_postsTry in
const params = new URLSearchParams({
  query: "coffee roaster",
});
const res = await fetch(`https://socialtap.dev/v1/x/search_posts?${params}`, {
  headers: { "x-api-key": process.env.SOCIALTAP_API_KEY ?? "" },
});
const body = await res.json();
if (!res.ok) throw new Error(`${body.error.code}: ${body.error.message}`);
const { data, page, meta } = body;
console.log(data, meta.credits_charged);
200 OK · GET https://socialtap.dev/v1/x/search_postsLong arrays and strings are shortened here. Real responses are complete.Docs

One schema on 6 platforms.

The response reference lists every field, its type and when it is null. See the full schema.

  • Null means unknown

    A field X doesn't show is null, never zero or an empty string, so a real zero always means zero.

  • What it accepts

    Words to find X posts by, as a web search reads them: a topic, a product, a phrase (coffee roaster, "blue bottle" review), or one #hashtag or @handle to find posts that show it.

  • Write one parser

    X, TikTok, Instagram and 3 more platforms answer in these fields, so the code that reads one reads them all.

platformstring
Platform the item is on.
typestring
The kind of item the result names, as the resource that describes it: profile (an account), post, hashtag, sound, place or community. The item's summary is the field of that name, and a filled result's record is details.<type>. A search that finds several kinds (a platform's top search) mixes them in one list. New values may be added as more kinds are searchable; treat unknown values as other.
positioninteger
Zero-based rank of the result in the list, across pages: the search engine's order, counting only the results kept.
urlstring
The item's canonical link on the platform (the account's page for a profile, the post's for a post).
matched_urlstring
The page the index listed: the item's own page, or one of its pages that names it (a video of an account, for a profile found through it).
titlestring
The page's title as the index shows it: often the item's name, but not the item's own field. Null when the index shows none.
snippetstring
The index's excerpt of the page: often the item's description and counts as the page stated them when it was indexed, days or weeks ago. Null when the index shows none.
profileobject
The account the result names (type profile): what its link and the index's text say of it, completed from details when the result is filled. Null for every other type.

What teams build with the X (Twitter) Post Search API.

  • Monitor what people say about a brand

  • Find posts with a hashtag or mention

  • Collect dated posts on a topic for research

  • Find sources and quotes for a story

Good to know before you build.

  • X has no logged-out search, so results come from a web search engine's index of X's post pages, in the engine's order. A post the index hasn't crawled isn't found.
  • There is no latest or top order: results come in the engine's ranking, which favors older posts when no date is set.
  • published_at is exact, read from the post's ID, and since and until filter by it. A post from before X's IDs carried a time (November 2010) has published_at null without fill.
  • A window of a day or a week can be thin or empty even for a common word, because the index holds only part of each day's posts.
  • since: and until: in the query are read as the since and until params. X's other operators (from:, lang:, min_faves:, filter: and similar) are refused rather than ignored, because a web search can't apply them.
  • Without fill, id and media are null, and text is the index's copy, often cut short (listed in approximate_fields).
  • text is null when the index's excerpt can't be told apart from the author's bio or a linked page's description, which is common on business and brand searches. snippet keeps the excerpt.
  • Without fill, views, likes and replies appear only where the index states them, and are approximate. With fill=true, each result's details.post is the post's live record from the X (Twitter) Post API, and its summary is updated from it.
  • A #hashtag or @handle alone is a weak fit next to X's own search: a popular tag's first page mostly shows it and later pages less, a rare or non-Latin tag can find little or nothing, and the tag's word without the # also matches.
  • An @handle finds posts that name the account, mixed with the account's own posts.
  • A result the post lookup can't fetch (a deleted post, a suspended account) stays unfilled and costs nothing extra, and meta.warnings says how many.
  • The index goes only so deep, so a search usually ends after two or three pages (page.end_reason end).
  • Case doesn't matter. The query's own site: operators are removed, and intitle:, inurl:, in: and similar operators are read as the plain words they name.

From 1 credit per page. Failed requests are free.

Buy credits once and spend them on any endpoint, on any platform.

SourcePrice per successful pagePer 1,000 pages
Any source1 credit + 1 per result filled in
up to 51 credits (50 results filled in)
$0.75–$1.97 + $0.75–$1.97 per result filled in
  • Cache hits are free.
  • Credits from packs and top-ups never expire.
  • A monthly plan's credits are spent first, and what is left of them ends at each renewal.
  • Prices exclude tax: sales tax is added at checkout where it applies.
  • Outside the US, plans and packs are sold to businesses: checkout asks for your VAT, GST or other business tax ID.

Questions about the X (Twitter) Post Search API.

More in the API reference.

Can I get the latest tweets on a topic?
Yes, with since. Results come by relevance, not time, so set since to a recent date for recent posts, and until to end the window.
How much does the X (Twitter) Post Search API cost?
A page of up to 50 posts costs 1 credit + 1 per result filled in, up to 51 credits (50 results filled in). Every successful page is charged, empty pages included. SocialTap credits cost $0.75–$1.97 per 1,000, depending on the plan or pack.
How do I get the next page?
Repeat the same request with cursor set to page.next_cursor from the previous response, keeping the other parameters. When page.has_more is false there are no more pages. Cursors expire after 24 hours.

Try it with your own search.

Type it in the playground, or copy the request into your code.

100free credits
  • No credit card
  • Failed requests are free
  • Works on all 218 endpoints
Start for free Read the docs