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 |
|---|---|---|---|---|---|
home-latest-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
home-latest-timeline
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-graphql
Retrieve the authenticated user's latest home timeline in real reverse-chronological order with a single GraphQL-powered API call.
The Twitter Graphql Home Latest Timeline API on ApiPass is an asynchronous task-based endpoint that lets you fetch the "Following" (Latest) tab of a Twitter/X home timeline — the same reverse-chronological feed of tweets from accounts the authenticated user follows. Built on top of Twitter's internal GraphQL layer, it returns a rich payload that includes full tweet content, media, engagement metrics (likes, retweets, replies, bookmarks, views), author profile data, promoted content flags, and timeline instructions. You submit a task via POST /api/v1/jobs/createTask using the twitter/graphql/home-latest-timeline model and retrieve results via GET /api/v1/jobs/recordInfo, with optional callback delivery when the job completes. The reverse chronological timeline endpoint returns Tweets that appear in a user's home timeline, with the most recent Tweets first.
Skip the lengthy X Developer approval process, project setup, and OAuth 1.0a/2.0 configuration. Get started with just an ApiPass API key.
Unlike the trimmed-down v2 REST response, you receive the same deep object structure Twitter's own web client consumes, including card data, view counts, conversation controls, and promoted metadata.
The channel: auto parameter automatically allocates your task across available providers based on real-time pricing and stability metrics to balance minimal cost and reliable performance.
Choose between starter (ultra-low-cost), regular (standard, priced far below official APIs), or official (native Twitter API pricing with maximum stability) to match your budget and reliability needs.
Submit a job, get a taskId instantly, and either poll for results or receive a push notification via your callBackUrl — ideal for high-volume, non-blocking workloads.
Every task returns a standardized envelope with code, message, state, costTime, and resultJson fields, making error handling and monitoring straightforward.
eturns tweets exactly in the order they were posted by followed accounts, with no algorithmic ranking, mirroring the "Latest" tab in the official Twitter/X client.
Control the number of tweets returned via count, toggle promoted content with includePromotedContent, opt into latestControlAvailable, and set requestContext (e.g., launch) to match specific client behaviors.
Each entry includes the full tweet body, entities (URLs, mentions), author user_results with follower counts and verification status, engagement counters, view state, source attribution, and timeline instructions like TimelineAddEntries and TimelineShowCover.
Power third-party reader apps and browser extensions that display a pure chronological feed without ads or algorithmic re-ranking.
Continuously pull the latest tweets from a curated following graph to feed brand-monitoring, PR, or competitor-tracking dashboards.
Trigger notifications (Slack, Discord, email, SMS) whenever specific accounts you follow publish new tweets containing target keywords.
Stream your following feed into LLM pipelines for summarization, sentiment scoring, topic clustering, or personalized daily digests.
See how ApiPass streamlines access, expands response depth, and removes the friction of Twitter's official developer platform.
The official endpoint requires OAuth 1.0a User Context or OAuth 2.0 Authorization Code with PKCE, plus an approved X Developer account and project. ApiPass replaces this entire flow with a single Bearer token — no app registration, no OAuth handshake, no user-context tokens to refresh.
The official v2 reverse chronological home timeline endpoint returns the most recent Tweets and Retweets posted by the authenticated user and the accounts they follow, but in a flattened REST format with strict rate ceilings (up to 180 requests per 15 minutes, with a limit of up to 3,200 tweets). ApiPass proxies Twitter's native GraphQL response — the same one used by twitter.com — giving you card bindings, conversation controls, view counts, promoted metadata, and timeline covers that the v2 REST endpoint omits, all under ApiPass's task-based quota system rather than per-user rate limits.
Journalists and newsrooms following hundreds of sources can pull the latest posts every minute to surface breaking stories before they trend.
Track cashtag mentions and analyst commentary from a followed list of finance influencers in true chronological order for time-sensitive trading signals.
Agencies managing multiple brand accounts can programmatically review each account's home timeline to spot conversations worth engaging with.
Collect timeline snapshots at fixed intervals to study information diffusion, network effects, or content velocity across a defined follow graph.
Sign up on ApiPass and generate a Bearer token from your dashboard.
Send a POST request to the /api/v1/jobs/createTask endpoint using the model identifier twitter/graphql/home-latest-timeline. Configure your input variables such as count (number of tweets to fetch), includePromotedContent (toggle ads), latestControlAvailable, and requestContext. Optionally provide a callBackUrl if you want ApiPass to push the result to your server the moment the task completes.
ApiPass returns a taskId immediately. Query task status via the /api/v1/jobs/recordInfo endpoint using that ID — once the state field turns to success, the full GraphQL timeline payload will be available in data.resultJson, ready to parse for tweet entries, author profiles, engagement metrics, and timeline instructions. If you set a callback URL, you can skip polling entirely and process the result the moment it arrives.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get the Home Latest 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 "count":"number",
8 "includePromotedContent": "boolean",
9 "latestControlAvailable": "boolean",
10 "requestContext": "string",
11 }
12 }
13}modelRequiredstringThe model name to use for generation
"twitter/graphql/home-latest-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.countRequirednumber20
input.variables.includePromotedContentOptionalbooleanfalse
input.variables.latestControlAvailableOptionalbooleantrue
input.variables.requestContextOptionalstringlaunch
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/home-latest-timeline",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "variables": {
9 "count": 20,
10 "includePromotedContent": False,
11 "latestControlAvailable": True,
12 "requestContext": "launch",
13 }
14 }
15 }'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
