X (Twitter) Comments API

Q: Can I pass the post link instead of the ID?

Not in id, which takes only the number. From a link like x.com/ /status/ , copy the number and send it as a string so its digits stay exact. tweet_id is accepted as a compatibility alias, but id remains required and takes priority.

Q: Which replies should I read first?

Sort by like_count to see which replies other readers agreed with, and check author_follower_count to spot replies from accounts with large audiences. Replies with a high reply_count mark where a sub-thread formed around one particular point.

POST

API health

Health data cannot be read right now, so this API's recent state is unknown. That does not mean it is down.

Collect the replies under an X (Twitter) post, each with text, author, the author's follower count and its own engagement numbers. Send the original post's numeric id; the full conversation is not guaranteed.

X (Twitter) Comments reads the replies posted under one X post, given that post's numeric id. Each row is one reply: what it says in full, its link, how many likes, reposts, replies and views it drew, when it went up, and who wrote it, down to that person's handle, display name, profile link and audience size. Brand, support and research teams use it to hear how people respond to a post: reactions to an announcement, customer complaints under a brand's post, or the tone of the conversation around a public statement.

The id you send identifies the original post, while the id on each returned row identifies a reply. A reply's own reply_count shows whether it started a side conversation, and author_follower_count tells you how far the reply author's voice carries. To read the original post's text and numbers, call the X (Twitter) Post details capability with the same id.

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.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra X (Twitter) Comments endpoint (twitter/comments).

Endpoint contract:
- 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 comments, and put the parameters inside params.
- Required parameters:
  - id: Numeric post ID for post or comments, corresponding to the digits following x.com/username/status/. It is recommended to store this as a string to prevent JavaScript large integer precision loss.
- Optional parameters:
  - tweet_id: Compatibility input for id, with lower precedence than id, which does not replace the required public id field.
  - limit: The most rows to return in this call, an integer from 1 to 50. 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.
- Example request body:
{
  "platform": "twitter",
  "action": "comments",
  "params": {
    "id": "2103610284464316469"
  }
}
- 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	`comments`	Capability identifier, fixed value.
`id`	body.params	Not declared	Yes	-	Numeric post ID for post or comments, corresponding to the digits following x.com/username/status/. It is recommended to store this as a string to prevent JavaScript large integer precision loss; do not pass full URLs into id.
`tweet_id`	body.params	Not declared	No	-	Compatibility input for id, with lower precedence than id, which does not replace the required public id field.
`limit`	body.params	`integer (1–50)`	No	`20`	The most rows to return in this call, an integer from 1 to 50. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

Code samples

bash

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": "comments",
  "params": {
    "id": "2103610284464316469"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.

json

{
  "id": "req_…",
  "platform": "twitter",
  "action": "comments",
  "results": [
    {
      "id": …,
      "url": …,
      "text": …,
      "like_count": …,
      "retweet_count": …,
      "reply_count": …,
      "view_count": …,
      "posted_at": …,
      "author_username": …,
      "author_name": …,
      "author_url": …,
      "author_follower_count": …,
      "platform": …
    }
  ],
  "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.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

Can I pass the post link instead of the ID?

Not in id, which takes only the number. From a link like x.com/<handle>/status/<number>, copy the number and send it as a string so its digits stay exact. tweet_id is accepted as a compatibility alias, but id remains required and takes priority.

Which replies should I read first?

Sort by like_count to see which replies other readers agreed with, and check author_follower_count to spot replies from accounts with large audiences. Replies with a high reply_count mark where a sub-thread formed around one particular point.

What does an empty result mean?

No rows means no public replies came back for that post ID: the post may have no replies, or the number may not belong to a post. Check the id against the post's link before you retry. Calls that come back empty are not charged.

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

X: Original Post ID, Conversation ID, and Reply Relationships ↗
X uses conversation_id to indicate the original post ID that initiated a conversation, which multi-level replies can share; reconstructing parent-child relationships requires parent post identifiers. This endpoint does not expose these relationship fields, so official example reply trees should not be expected in current output.
Checked 2026-09-04