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 |
|---|---|---|---|---|---|
user-tweets otherTwitter | Starter | 0.01per post | $0.00005 | - | - |
Competitor pricing costs $45.440 more
ApiPass is 90.90% lower, estimated at multiple calls returning 10,000 returned posts total
user-tweets
ApiPass Price
$0.0005
0.1 credits per post
Competitor Prices
Complete guide to using twitter-api-simple
Fetch a Twitter user's latest tweets in real time with a single, unified API call through ApiPass.
The Twitter Simple User Tweets API on ApiPass is a streamlined endpoint that lets developers retrieve tweets posted by any public Twitter (X) user without the complexity of managing OAuth flows, rate limits, or scraping infrastructure. Built on top of ApiPass's unified jobs API, it accepts a simple task envelope with your query parameters and returns structured tweet data — including tweet IDs, text content, and pagination cursors — so you can integrate Twitter content into your applications, dashboards, or data pipelines in minutes. Whether you need to monitor a single account, aggregate posts from influencers, or build a social listening tool, this API provides a fast, reliable, and developer-friendly way to access Twitter user timelines.
Skip the lengthy Twitter developer application process and OAuth 2.0 setup. A single Bearer token authenticates every request to ApiPass.
All Twitter endpoints share the same model + input request structure, so once you learn one ApiPass API, you've learned them all.
Use the next_cursor_str returned in each response as the cursor parameter on your next request to seamlessly walk through long tweet histories.
Tasks are created and queried separately via createTask and recordInfo, allowing you to handle large workloads without blocking your application threads.
Pass a callBackUrl when creating a task and ApiPass will notify your server the moment results are ready — no polling required.
Every response follows the same { code, message, data } envelope, making error handling and parsing trivial across your entire codebase.
Pass a search query q and an optional sort_by mode (Top, Latest, People, Photos, or Videos) to instantly filter the kind of content you want returned.
Each result set includes a next_cursor_str you can feed back in as input.cursor to fetch the next page of tweets in chronological order.
Results are delivered inside a resultJson object containing a tweets array with tweet_id, text, and other fields ready for direct consumption by your application.
Display real-time tweets from key accounts, brand mentions, or trending topics inside internal analytics tools.
Monitor influential accounts for keywords like "eth" or "btc" and trigger alerts, trades, or notifications based on sentiment.
Build news feeds, newsletter digests, or curated timelines that pull tweets from a list of trusted sources automatically.
Collect large volumes of recent tweets to train LLMs, sentiment classifiers, or trend-prediction models with up-to-date data.
See how ApiPass simplifies access to Twitter user tweets compared to the official Twitter API, removing setup friction and unifying endpoints under one consistent interface.
Twitter's official API requires developer account approval, app registration, OAuth configuration, and tier-based pricing. ApiPass replaces all of that with a single Authorization: Bearer YOUR_API_KEY header.
Instead of learning dozens of distinct Twitter v2 endpoints, ApiPass exposes every Twitter capability through one consistent /api/v1/jobs/createTask interface — just change the model field (e.g. twitter/simple/search) to switch operations.
Track every public mention of your brand, product, or competitor and feed the results into your CRM or alerting system.
Pull the latest tweets from a list of influencers to measure posting frequency, engagement, and topical relevance.
Aggregate public sentiment around products, events, or hashtags to inform marketing campaigns and product decisions.
Continuously scan tweets for regulatory keywords, leaked information, or reputational risks affecting your organization.
Sign up at ApiPass and generate an API key from your dashboard. You'll pass it as an Authorization: Bearer header on every request, so there's no OAuth setup or Twitter developer application required.
Send a POST request to the /api/v1/jobs/createTask endpoint with model set to twitter/simple/search and your search parameters inside the input object — including the query text q, an optional sort_by mode, and an optional pagination cursor. The response will return a unique taskId you can use to retrieve results.
Use the returned taskId to call the /api/v1/jobs/recordInfo endpoint. Once the task state becomes success, the resultJson field will contain the tweets array along with a next_cursor_str you can feed back into a new task to fetch the next page of results.
All APIs require authentication via Bearer Token.
Authorization: Bearer
Create a task to get user tweets
The API accepts a JSON payload with the following structure:
1{
2 "model": "string",
3 "callBackUrl": "string (optional)",
4 "channel": "auto",
5 "input": {
6 "user_id": "string"
7 }
8}modelRequiredstringThe model name to use for generation
"twitter/simple/user-tweets"
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.user_idRequiredstringUser ID
44196397
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/user-tweets",
6 "callBackUrl": "https://your-domain.com/api/callback",
7 "input": {
8 "user_id": "44196397"
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
