X (Twitter) Posts by user API
API health
- 24h health
- 100%
- 24h average time
- 31.31 s
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Pull an X (Twitter) account's posts with likes, reposts, replies and views for each, plus publish time. One batch may not hold every post, reply or repost, and private messages are never included.
Send POST https://api.everyinfra.com/api/v1/social with platform set to twitter and action set to user_posts. Price $0.56 per 1,000 requests ($0.000556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
X (Twitter) Posts by user reads what one X account has posted publicly, given the account's handle in username. For each post you get the text in full, its link and ID, the like, repost, reply and view counts, when it was published, and the author's handle, display name, profile link and follower count. Communications teams, researchers and analysts use it to see what an account has been saying and which posts landed: following a public figure's or brand's statements, benchmarking engagement against competitors, or archiving an account's output for later analysis.
Name the account by its handle, with or without the @, not by its profile link. retweet_count counts reposts and reply_count counts replies, and together with like_count they are the engagement measures to compare. posted_at is an ISO 8601 time in UTC; parse it defensively, since a non-standard string from the platform is passed through as is.
AI prompt
#Please help me write a data collection script with the EveryInfra X (Twitter) Posts by user endpoint (twitter/user_posts).
How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to twitter and action to user_posts, and put the parameters inside params.
- Required parameters:
- username: X username, optionally prefixed with @, without entering a full profile URL. profile compiles data from author details within recent posts.
- Optional parameters:
- limit: The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, url, text, like_count, retweet_count, reply_count, view_count, posted_at, author_username, author_name, author_url, author_follower_count; 37 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=twitter.
- Example request body:
{
"platform": "twitter",
"action": "user_posts",
"params": {
"username": "nasa"
}
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
#| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | twitter | Platform identifier, fixed value. |
action | body | string | Yes | user_posts | Capability identifier, fixed value. |
username | body.params | string | Yes | - | X username, optionally prefixed with @, without entering a full profile URL. profile compiles data from author details within recent posts; followers_list and following_list retrieve visible followers and following accounts respectively. |
limit | body.params | integer (1–200) | No | 20 | The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
Code samples
#curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "twitter",
"action": "user_posts",
"params": {
"username": "nasa"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
#{ "id": "req_…", "platform": "twitter", "action": "user_posts", "results": [ { "id": "•••", "url": "https://x.com/NASA/status/2103610284464316469", "text": "With @•••, we’ll provide an update on Starliner development and plans for regular crew flights to and from the @••• Watch live Monday, Sept. 28 at 3pm ET: https://t.co/bxg2gpZzog https://t.co/OJaD49OyHh", "like_count": 2460, "retweet_count": 312, "reply_count": 119, "view_count": 558723, "posted_at": "Fri Sep 25 22:19:09 +0000 2026", "author_username": "NASA", "author_name": "NASA", "author_url": "https://x.com/•••", "author_follower_count": 92375074, "platform": "twitter" }, { "id": "•••", "url": "https://x.com/NASA/status/2103589735449141451", "text": "@••• 🤭", "like_count": 61, "retweet_count": 1, "reply_count": 7, "view_count": 5641, "posted_at": "Fri Sep 25 20:57:30 +0000 2026", "author_username": "NASA", "author_name": "NASA", "author_url": "https://x.com/•••", "author_follower_count": 92375074, "platform": "twitter" } ], "count": 20, "billing": { "charged": …, "charged_usd": …, "balance_after_usd": …, … }, "quota": { … }}
Response fields
#Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
url | Link to the record on the platform. |
text | Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so). |
like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
retweet_count | Keeps the platform's own meaning |
reply_count | Replies, usually replies to a comment. null means not disclosed. |
view_count | Views or plays. null means not disclosed, not 0. |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
author_username | Author's username (@handle), usually usable in URLs. |
author_name | Author's display name. |
author_url | Link to the author's profile on the platform. |
author_follower_count | Author's follower count. null means not disclosed. |
quote_count | Keeps the platform's own meaning |
bookmark_count | Keeps the platform's own meaning |
language | Content language code (for example zh, en) as judged by the platform; it can be wrong. |
conversation_id | Keeps the platform's own meaning |
is_reply | Keeps the platform's own meaning |
is_quote | Keeps the platform's own meaning |
is_repost | Keeps the platform's own meaning |
is_pinned | Keeps the platform's own meaning |
reply_to_id | Keeps the platform's own meaning |
reply_to_user_id | Keeps the platform's own meaning |
reply_to | Keeps the platform's own meaning |
source | Keeps the platform's own meaning |
media | Keeps the platform's own meaning |
hashtags | Hashtags in the text, in order of appearance; absent when there are none. |
mentions | Keeps the platform's own meaning |
links | Keeps the platform's own meaning |
author_id | Author's unique ID on the platform. |
author_avatar_url | Keeps the platform's own meaning |
author_bio | Keeps the platform's own meaning |
author_is_verified | Keeps the platform's own meaning |
author_following_count | Keeps the platform's own meaning |
author_post_count | Keeps the platform's own meaning |
author_media_count | Keeps the platform's own meaning |
author_created_at | Keeps the platform's own meaning |
author_banner_url | Keeps the platform's own meaning |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
FAQ
#Why is view_count null on some posts?
#Null means the view count was not disclosed for that post; it does not mean nobody saw it. Compare such posts on like_count, retweet_count and reply_count instead, and keep them out of any average of views so the missing values do not distort it.
How do I read the replies to one of these posts?
#Take the number after /status/ in the row's url and pass it as the post ID to the X (Twitter) Comments capability, which lists the replies under that post. Keep the ID as text: X post IDs are longer than JavaScript numbers can hold exactly, so converting one to a number changes it.
How do I compare engagement between accounts of different sizes?
#Divide like_count, retweet_count and reply_count by author_follower_count to get engagement per follower, which puts a large and a small account on the same scale. Store the follower figure with each batch rather than reusing an old one, since audiences change between calls.
Errors and billing
#- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.
Official references
#Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.
- X: username / handle vs. Display Name ↗
X separates the handle from the display name; the handle forms the @ identifier and profile link, and once changed, the original handle may be claimed by others. When archiving, do not rely solely on display names or mutable handles to verify identity.
Checked 2026-09-04