Cookie Preferences
We use cookies to personalize content and analyze traffic. See our Cookie Policy.
No output yet. Submit the form to generate content.
Transparent pricing with no hidden fees. Pay as you go.
| Rule & Modality | Channel | Credits | Price (USD) | Official / Reference Price | Daily Savings |
|---|---|---|---|---|---|
search-timeline otherTwitter | Starter | 0.01per post | $0.00005 | - | - |
Competitor pricing costs $45.450 more
ApiPass is 90.90% lower, estimated at multiple calls returning 10,000 returned posts total
search-timeline
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Search Twitter's timeline programmatically and retrieve real-time tweet results by keyword, hashtag, or advanced query.
The Twitter Graphql Search Timeline API on ApiPass is a task-based endpoint that lets developers query Twitter's (X's) search timeline through the same GraphQL schema used by Twitter's native clients. By sending a POST request to /api/v1/jobs/createTask with the model twitter/graphql/search-timeline, you can submit a raw search query (keywords, hashtags, operators, or user handles) and receive a structured JSON payload containing matching tweets, author profiles, media entities, engagement metrics, and pagination cursors. The API supports multiple result modes such as Latest and returns the full GraphQL response, giving you the same depth of data that powers Twitter's own search interface — without the complexity of managing OAuth, rate limits, or scraping infrastructure.
Skip the lengthy application, approval, and elevated-access process. A single ApiPass API key unlocks the endpoint immediately.
Get the exact same rich data structure Twitter's native web client uses, including tweet_results, user_results, media variants, view counts, and highlight ranges.
With the default channel: auto setting, ApiPass automatically balances your requests across starter, regular, and official providers based on real-time pricing and stability for the best cost-to-reliability ratio.
Submit search jobs and poll or receive callbacks via callBackUrl, making it ideal for large-scale crawling, batch pipelines, and long-running workloads.
Use the cursor parameter to walk through thousands of matching tweets beyond what a single page returns.
Choose the provider tier that fits your budget: ultra-low-cost starter, cost-efficient regular, or official for pricing identical to Twitter's own service with premium stability.
The rawQuery parameter accepts anything from simple keywords ("twitter") to complex Twitter search operators, hashtags, from: filters, date ranges, and language flags.
Switch between search products such as Latest via the product parameter to retrieve chronologically fresh tweets, and control page size with count (default 40).
Each entry includes full text, media (images, GIFs, video variants), user profile details, timestamps, reply/retweet/favorite counts, view counts, and conversation threading fields.
Monitor brand mentions, competitor activity, or breaking news keywords and surface them in analytics tools.
Feed the raw tweet stream into NLP models to track sentiment shifts around products, elections, or market events.
Watch cashtags ($BTC, $TSLA) or influencer handles and trigger alerts, trades, or Discord/Telegram notifications on relevant tweets.
Auto-curate tweet embeds by hashtag or topic for blogs, live-event pages, and journalist research dashboards.
Compare how ApiPass and Twitter's official developer platform differ in access requirements and the depth of data returned from a search request.
Twitter's official v2 Search API requires a paid developer subscription (Basic, Pro, or Enterprise tier), project approval, and OAuth 2.0 setup before you can issue a single request. ApiPass requires only a Bearer API key — you can create a task within minutes of signing up, with no gatekeeping tiers for basic search access.
Twitter's official REST v2 endpoint returns a flattened, field-selected JSON limited by the tweet.fields / user.fields you request, and omits many internal signals. ApiPass returns the raw GraphQL response (search_by_raw_query.search_timeline.timeline.instructions) that mirrors Twitter's own web client, exposing richer objects like views.count, edit_control, highlights.textHighlights, clientEventInfo, and full media video_info.variants — data that is either hidden or requires premium tiers on the official API.
Continuously search for mentions of your company, product SKUs, or executives, and route negative sentiment to customer-support workflows.
Collect large historical or real-time tweet datasets around specific topics, hashtags, or geolocations for quantitative research.
Search niche keywords, rank the resulting authors by followers_count, favourites_count, and engagement, and identify emerging voices in a vertical.
Search competitor campaign hashtags or slogans to benchmark reach, engagement, and creative angles being used across the platform.
Sign up on ApiPass and generate a Bearer token from your dashboard. This single key authenticates all your requests, so no OAuth flow or Twitter developer application is needed.
Send a POST request to the /api/v1/jobs/createTask endpoint with the model set to twitter/graphql/search-timeline and include your search parameters inside input.variables — at minimum a rawQuery, plus optional fields like count, product, and cursor. Optionally provide a callBackUrl to receive a push notification when the job completes.
Take the taskId returned from step 2 and query the /api/v1/jobs/recordInfo endpoint. Once the task state becomes success, parse the resultJson field for the full list of matching tweets, and use the returned pagination cursor to fetch additional pages as needed.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Search the timeline.
The API accepts a JSON payload with the following structure:
1{
2 "model": "string",
3 "callBackUrl": "string (optional)",
4 "channel": "auto",
5 "input": {
6 "variables": {
7 "rawQuery": "string",
8 "count": "number",
9 "cursor": "string",
10 "querySource": "string",
11 "product": "string",
12 "includePromotedContent": "boolean",
13 }
14 }
15}modelRequiredstringThe model name to use for generation
"twitter/graphql/search-timeline"
callBackUrlOptionalstringCallback URL for task completion notifications. If omitted, no callback will be sent.
"https://your-domain.com/api/callback"
channelOptionalstringYou may specify the corresponding provider within APIPASS via the channel parameter; these providers handle the actual image and video generation tasks. APIPASS currently offers three provider options:
The default value for the channel parameter is auto. When enabled, APIPASS automatically allocates tasks across available providers based on real-time pricing and stability metrics to balance minimal cost and reliable performance. Retain the default auto value unless you have custom routing requirements.
Available options:
auto
The input object contains the following parameters:
input.variables.rawQueryRequiredstringinput.variables.countOptionalnumber40
input.variables.cursorOptionalstringinput.variables.querySourceOptionalstringtyped_query
input.variables.productOptionalstringLatest
input.variables.includePromotedContentOptionalbooleanfalse
1curl -X POST "https://api.apipass.dev/api/v1/jobs/createTask" \
2 -H "Content-Type: application/json" \
3 -H "Authorization: Bearer YOUR_API_KEY" \
4 -d '{
5 "model": "twitter/graphql/search-timeline",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "variables": {
9 "rawQuery": "twitter",
10 "count": 40,
11 "cursor": "",
12 "querySource": "typed_query",
13 "product": "Latest",
14 "includePromotedContent": false,
15 }
16 }
17 }'1{
2 "code": 200,
3 "message": "success",
4 "data": {
5 "taskId": "task_12345678"
6 }
7}codeStatus code, 200 for success, others for failure
messageResponse message, error description when failed
data.taskIdTask ID for querying task status and results
