X (Twitter) Posts in bulk API
API health
- 24h health
- Normal
- Healthy / normal
- Available
Last 24 hours
Last 30 days
Look up as many as 20 X (Twitter) posts at once from urls, each a post link or numeric post ID. Each post found is one row with the same fields as post, plus input, the entry you sent. Billed per post; posts not found are listed in missed and not charged.
Send POST https://api.everyinfra.com/api/v1/social with platform set to twitter and action set to posts_batch. Price $0.56 per 1,000 requests ($0.000556 per call). Failed calls and empty results are not charged. Each element in urls counts as one call: the number of elements you send sets the charge. Synchronous only: everything it returns (every target of a batch, or every SKU of a product) is read within this call, and "mode": "async" returns a 422 before any charge.
AI prompt
#Please help me write a data collection script with the EveryInfra X (Twitter) Posts in bulk endpoint (twitter/posts_batch).
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 posts_batch, and put the parameters inside params.
- Required parameters:
- urls: The posts to read, as an array of up to 20 entries (not a comma-separated string). Each entry is a post link https://x.com/<username>/status/<ID> or a numeric post ID, and each post can appear only once.
- Optional parameters:
- limit: The most rows to return in this call, an integer of 1 or more. The default applies when you leave it out, and a call can return fewer rows.
- 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; 32 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=twitter.
- Example request body:
{
"platform": "twitter",
"action": "posts_batch",
"params": {
"urls": [
"https://x.com/NASA/status/2119833829389041896",
"2113338155088961899"
]
}
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- This endpoint runs synchronously only; do not add "mode": "async" to the body.
- 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 | posts_batch | Capability identifier, fixed value. |
urls | body.params | array | Yes | - | The posts to read, as an array of up to 20 entries (not a comma-separated string). Each entry is a post link https://x.com/<username>/status/<ID> or a numeric post ID, and each post can appear only once. Billed per post; posts not found are not charged and are listed in missed. |
limit | body.params | integer (1–) | No | - | The most rows to return in this call, an integer of 1 or more. The default applies when you leave it out, and a call can return fewer rows. |
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": "posts_batch",
"params": {
"urls": [
"https://x.com/NASA/status/2119833829389041896",
"2113338155088961899"
]
}
}'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": "posts_batch", "results": [ { "id": …, "url": …, "text": …, "like_count": …, "retweet_count": …, "reply_count": …, "view_count": …, "posted_at": …, "author_username": …, "author_name": …, "author_url": …, "author_follower_count": …, "quote_count": …, "bookmark_count": …, "language": …, "conversation_id": …, "is_reply": …, "is_quote": …, "is_repost": …, "reply_to_id": …, "reply_to_user_id": …, "reply_to": …, "media": …, "hashtags": …, "mentions": …, "links": …, "author_id": …, "author_avatar_url": …, "author_bio": …, "author_is_verified": …, "author_created_at": …, "platform": …, "input": … } ], "count": …, "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 |
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 |
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_created_at | Keeps the platform's own meaning |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
input | Keeps the platform's own meaning |
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.