Twitter/X Search Tweets API
Returns tweets matching a keyword or phrase, each with the full text, like, retweet, reply, bookmark and view counts, media attachments, author info, and creation time.
10–50 credits, metered · cursor pagination · failed calls free · 10 free calls to start
curl "https://api.insightsocial.app/v1/twitter/search/tweets?query=nike+running+shoes" \-H "x-api-key: $INSIGHTSOCIAL_API_KEY"
When to use it
Use it to track a topic or brand across X. Operators like from:, quoted phrases, filter:images, and since:/until: work inside query; sort picks latest (default) or top, the cursor pages deeper.
Parameters
Query parameters for GET /v1/twitter/search/tweets. Send your key in the x-api-key header.
| Name | Required | Description |
|---|---|---|
| query | Yes | Keyword or phrase to search tweets for. X operators inside this string narrow the search itself, for example since_time: and until_time: in Unix seconds, from:handle, quoted phrases, min_faves:20, filter:images, and filter:videos. Quote a multi-word phrase when you want relevance rather than engagement ranking from sort=top |
| sort | No | Result ranking: latest (default) for the newest matches first, top for the most popular matches. top ranks by engagement, not relevance, so an unquoted multi-term query can return popular posts that match none of your terms. Quote the phrase or add an operator to tighten it |
| cursor | No | Cursor from the previous response's pagination.next_cursor to fetch the next page |
| since | No | Only posts published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. It is sent to X as since_time: inside your query, from 00:00 UTC of that day, so the pages hold posts inside the window, and every row is checked again here. The walk ends when X has no more posts in the window: next_cursor is not returned, has_more is false and pagination.stopped_at is since, usually on a last page with no posts, which is free. With a time of day, the page that reaches a post older than it ends the walk the same way. Sending it sets sort=latest (any other sort value is a free 400). A page with posts costs what a page costs. A row with no date is kept. A since: or since_time: operator you put in query yourself is sent as you wrote it, and nothing is added for that side. |
| until | No | Only posts published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. It is sent to X as until_time: inside your query, up to the midnight after that UTC day, so the first page starts at the end of the window and newer posts are never walked, and every row is checked again here. A row with no date is kept. An until: or until_time: operator you put in query yourself is sent as you wrote it, and nothing is added for that side. |
| 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. |
| 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. |
| sort_rows | No | views: orders the kept rows by view count, highest first. Rows without a view count go last. newest: orders the kept rows by publish date, newest first. Rows without a date go last. The sort covers only the rows this call collected over the pages it walked, not the whole feed. Every collected row is returned. A call that resumes from pagination.next_cursor sorts its own rows and does not merge them with the earlier ones. |
| max_pages | No | 1 to 50 (default 1). Walk up to this many pages in one call and return the rows from all of them (after any filter). |
| max_age_s | No | The oldest cached copy you accept, in seconds. A copy that old or younger is served, with its age in age_s and the X-Cache-Age header. Without it a copy up to 120 seconds old is served. A lower value fetches fresh (billed) when the copy is older, and 0 always fetches live, like Cache-Control: no-cache. |
Response fields
The same unified schema every typed endpoint returns, so code written for Twitter/X reads the other platforms too. A field the platform did not provide is null and listed in unavailable.
| Field | Type | Notes |
|---|---|---|
| id | string | An identifier, always a string. Never parse it as a number: several platforms use ids above 2^53. |
| url | string | null | |
| kind | string | null | The format of the post. Format words only, never a platform name. short = short-form vertical video (a reel, a TikTok, a YouTube Short). |
| content.text | string | null | |
| content.media_urls | array | null | |
| content.thumbnail_url | string | null | |
| content.duration_seconds | number | null | |
| author.id | string | null | |
| author.username | string | null | |
| author.display_name | string | null | |
| author.avatar_url | string | null | |
| author.verified | boolean | null | |
| engagement.views | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| engagement.likes | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| engagement.comments | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| engagement.shares | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| engagement.saves | integer | null | A count. null when the platform does not expose it; 0 only when it is really zero. |
| flags.nsfw | boolean | null | |
| flags.spoiler | boolean | null | |
| flags.pinned | boolean | null | |
| flags.deleted | boolean | |
| flags.likes_hidden | boolean | null | |
| flags.comments_hidden | boolean | null | |
| flags.shares_hidden | boolean | null | |
| flags.views_hidden | boolean | null | |
| flags.saves_hidden | boolean | null | |
| published_at | string | null | ISO-8601 timestamp in UTC, ending in Z. |
| language | string | null | The content's language as the platform states it, e.g. en, pt-BR. Detected languages come later (§7.1). |
| ext | object | null | Platform-specific fields, snake_case. |
Every field, error and example is in the Twitter/X Search Tweets API reference.
How much does the Twitter/X Search Tweets API cost?
Metered: 10–50 credits a call. The ceiling is reserved when the call starts and you are charged what it actually read.
Failed calls are free
A call that errors or finds nothing costs 0 credits.
Know the price first
Add dry_run=1 and the response quotes the call without making it. Nothing is charged.
One balance
API calls and Chrome extension exports share the same credits, on the free plan too.
Twitter/X Search Tweets API: frequently asked questions
Send GET /v1/twitter/search/tweets with the query parameter and your key in the x-api-key header. Returns tweets matching a keyword or phrase, each with the full text, like, retweet, reply, bookmark and view counts, media attachments, author info, and creation time.
Metered: 10–50 credits a call. The ceiling is reserved when the call starts and you are charged what it actually read. A call that errors or finds nothing costs 0 credits. A repeat call is charged again: the full price when it fetches new data, 2 credits when the answer comes from the shared cache. Add fresh=1 to force a new read. Only a retry with the same Idempotency-Key is free. Pro's 10,000 monthly credits cover about 1,000 calls at 10 credits each (about $0.01 a call). Add dry_run=1 to see the price of a call without making it.
No. There is no Twitter/X app, OAuth flow or app review. One InsightSocial API key works for this endpoint and every other platform, and your first 10 calls priced at 100 credits or less are free.
This endpoint pages. Each response carries pagination.next_cursor and pagination.has_more. Send next_cursor back unchanged as the cursor parameter and stop when has_more is false. Every page is a separate call and is charged as one.
You get an error or an empty result, and it costs 0 credits. The API reads public Twitter/X data only, so private accounts and deleted content come back as not found rather than as partial data.
Yes. Add the hosted MCP server at https://api.insightsocial.app/mcp to your AI app and sign in. The assistant finds this endpoint by name, shows its price and calls it with your credits.
Guides that use this endpoint
More Twitter/X endpoints
- Twitter/X Search Users API10 credits
- Twitter/X Profile API10 credits
- Twitter/X Communities Members API20 credits
- Twitter/X User Tweets API10 credits
- Twitter/X Communities Search API20 credits
- Twitter/X Tweet API10 credits
- Twitter/X Friendships API20 credits
- Twitter/X Community API10 credits
- Twitter/X Lists API20 credits
- Twitter/X Community Tweets API10 credits
- Twitter/X Lists Followers API20 credits
- Twitter/X Lists Members API20 credits