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 |
|---|---|---|---|---|---|
tweet-detail 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
tweet-detail
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-simple
Retrieve the full content, metadata, engagement metrics, and reply thread of any public tweet on X (Twitter) using just a tweet ID.
The Twitter Simple Tweet Detail API on ApiPass is a lightweight endpoint that lets developers pull complete information about a specific tweet by simply providing its unique tweet ID. In one call, you receive the original tweet's text, media attachments, author profile, timestamps, and rich engagement metrics such as view count, likes, retweets, quotes, and replies. In addition, the endpoint returns the associated reply thread, giving you a full conversational context around the tweet. Built on an asynchronous task-based architecture, the API is designed to be simple to integrate, stable at scale, and free from the complexity of managing Twitter's official developer tokens.
Skip the lengthy application, approval, and quota-tier process. A single ApiPass API key unlocks immediate access.
Pass one parameter (tweet_id) and get back a fully structured JSON payload including tweet body, media, author profile, and reply thread.
Submit a task, receive a taskId, and either poll recordInfo or receive results through a callBackUrl—ideal for pipelines handling high volumes.
Access view count, favorite count, retweet count, quote count, and reply count in a single response, without stitching multiple endpoints together.
Beyond the primary tweet, the response includes replies with their own author details and metrics, giving you native conversational context.
Pay-as-you-go pricing with no monthly platform fees, making it easier to scale from prototype to production.
Returns text, media URLs, media type, creation time, and flags like is_reply, is_quote, is_retweet, and is_self_send.
Each tweet comes packaged with the author's screen name, display name, verified status, follower count, statuses count, profile image, and account creation date.
Reply tweets include related_user_id and related_tweet_id fields, letting you reconstruct threads and quote chains programmatically.
Track how specific tweets perform in near real time, visualizing view counts, likes, and reply volume for brand or campaign monitoring.
Power internal tools, newsletters, or CMS plugins that render high-fidelity tweet previews from a tweet URL or ID.
Feed structured tweet data and reply threads into LLMs or sentiment models for tone analysis, topic clustering, or trend detection.
Fetch detailed engagement and reply data around sensitive tweets so PR and compliance teams can respond quickly with full context.
Twitter's official GET /2/tweets/:id endpoint requires a paid developer account, project setup, bearer tokens, and strict monthly quotas. ApiPass replaces all of that with a single API key, allowing you to start building in minutes.
The official endpoint often requires additional expansions and fields parameters (and extra requests) to include author profiles, media, and reply context. ApiPass returns the tweet, author profile, media, engagement metrics, and reply thread in one unified JSON response.
Automatically pull metrics for tweets by tracked influencers to measure ROI on partnerships and sponsored content.
Embed source tweets with accurate live counts in news articles, research reports, or curated feeds.
Analyze reply threads to gauge audience reaction to product launches, announcements, or public statements.
Snapshot tweet content and engagement at a point in time for legal, financial, or regulatory record-keeping.
Create a free ApiPass account at apipass.dev and generate a bearer key from your dashboard.
Send a POST request to /api/v1/jobs/createTask with the model set to twitter/simple/tweet-detail and the target tweet_id in the input. You'll instantly receive a taskId.
Either poll /api/v1/jobs/recordInfo?taskId=... until the state is success, or provide a callBackUrl when creating the task and receive the full tweet detail payload pushed directly to your server.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Get tweet details.
The API accepts a JSON payload with the following structure:
1{
2 "model": "string",
3 "callBackUrl": "string (optional)",
4 "channel": "auto",
5 "input": {
6 "tweet_id": "string"
7 }
8}modelRequiredstringThe model name to use for generation
"twitter/simple/tweet-detail"
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.tweet_idRequiredstringTwitter post ID
"1694634492403843248"
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/simple/tweet-detail",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "tweet_id": "1694634492403843248"
9 }
10 }'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
