Quick Answer
The TwexAPI Get Replies by Post ID endpoint (/twitter/tweets//replies/page) returns the root post, a page of reply objects, and pagination fields for a post ID; keep one sort_by mode across the cursor chain. Authenticate with a Bearer Token on api.twexapi.io. Typical reads use about 5 Credits (~$0.05 per 1,000 under the published conversion), and qualifying paid plans publish 20+ QPS. New accounts receive 20,000 starting Credits. Full request and response fields are in this guide and at https://docs.twexapi.io.
FAQ
What does the Get Replies by Post ID endpoint return?
returns the root post, a page of reply objects, and pagination fields for a post ID; keep one sort_by mode across the cursor chain
Which sort modes and pagination fields does the replies endpoint use?
The request accepts sort_by values Recency, Relevance, or Likes, plus optional next_cursor after the first page. The response can contain root_tweet, reply data, has_next_page, and next_cursor. Keep the post ID and sort mode unchanged while paging.
What should I store when exporting a reply thread?
Store the root post once, raw reply rows, tweet_id, requested sort_by, page number, incoming and returned cursors, and fetch time. Deduplicate replies by post ID and persist the last successful cursor after every page so a failed job can resume.
Why use TwexAPI instead of the first-party developer API for this workflow?
For Get Replies by Post ID, TwexAPI provides Bearer-authenticated workflows documented at https://docs.twexapi.io. A typical post or profile read uses 5 Credits (about $0.05 per 1,000 under the published conversion), and qualifying paid plans publish 20+ QPS. New accounts receive 20,000 starting Credits. As of 2026-08-20, first-party developer API Post reads list at $5 per 1,000 resources and User reads at $10 per 1,000; official rate limits vary by endpoint and access level.
How much does this API workflow cost on TwexAPI?
A typical read uses about 5 Credits. Under the published conversion, 1,000 such reads use 5,000 Credits, or about $0.05; a 10,000-read job uses about 50,000 Credits. Actual costs vary by endpoint, so confirm the endpoint price and current plan at https://twexapi.io/pricing.
Replies are where a post becomes a conversation. If you are measuring launch feedback, tracking community response, or preparing moderation review data, you need more than the root tweet. You need the replies, the order you requested them in, and the cursor trail that explains how the dataset was collected.
For new integrations, use TwexAPI's paginated replies endpoint: POST /twitter/tweets/{tweet_id}/replies/page. It returns replies page by page and avoids the timeout risk that comes with trying to pull a large thread in one request.
Endpoint and Sort Modes
Answer: Endpoint and Sort Modes is implemented by calling the TwexAPI endpoint documented in this guide with a Bearer Token; batch or paginated requests reduce overhead to ~5 credits per call at 20+ QPS.
Send a POST request to:
https://api.twexapi.io/twitter/tweets/<tweet_id>/replies/pageThe path parameter is the root tweet ID. The JSON body supports:
| Field | Required | How to use it |
|---|---|---|
sort_by | No | Recency, Relevance, or Likes. Use one sort mode for the whole export. |
next_cursor | No | Leave empty on the first request. Pass the previous response's next_cursor to continue. |
The first page can include root_tweet along with the first data page of replies. Later pages return more replies plus has_next_page and next_cursor.
Fetch the First Page
Answer: Fetch the First Page means using TwexAPI Bearer APIs on api.twexapi.io for this user case. A typical read uses 5 Credits (about $0.05 per 1,000), and qualifying paid plans publish 20+ QPS. As of 2026-08-20, first-party developer API Post and User reads list at $5 and $10 per 1,000 resources; rate limits vary by endpoint.
Use Recency when you want a timeline-style export. Use Relevance or Likes only when ranking is part of the analysis.
curl --request POST \
--url https://api.twexapi.io/twitter/tweets/<tweet_id>/replies/page \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"sort_by": "Recency"
}'A simplified response looks like this:
1{
2 "code": 200,
3 "msg": "success",
4 "root_tweet": {
5 "tweet_id": "1803006263529541838",
6 "text": "<root tweet text>"
7 },
8 "data": [
9 {
10 "tweet_id": "1234567890123456789",
11 "text": "<reply text>",
12 "created_at": "Mon Jul 01 12:34:56 +0000 2025",
13 "user": {
14 "screen_name": "example_user"
15 }
16 }
17 ],
18 "has_next_page": true,
19 "next_cursor": "cursor_from_this_response"
20}Continue with next_cursor
Answer: Continue with next_cursor means using TwexAPI Bearer APIs on api.twexapi.io for this user case. A typical read uses 5 Credits (about $0.05 per 1,000), and qualifying paid plans publish 20+ QPS. As of 2026-08-20, first-party developer API Post and User reads list at $5 and $10 per 1,000 resources; rate limits vary by endpoint.
When has_next_page is true, pass the cursor into the next request. Keep the same tweet_id and sort_by throughout the export.
curl --request POST \
--url https://api.twexapi.io/twitter/tweets/<tweet_id>/replies/page \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
"sort_by": "Recency",
"next_cursor": "cursor_from_this_response"
}'Changing the sort mode during pagination makes the result harder to explain. If you need a second ranking view, run a separate export and label it clearly.
Python Export Script
Answer: Python Export Script means using TwexAPI Bearer APIs on api.twexapi.io for this user case. A typical read uses 5 Credits (about $0.05 per 1,000), and qualifying paid plans publish 20+ QPS. As of 2026-08-20, first-party developer API Post and User reads list at $5 and $10 per 1,000 resources; rate limits vary by endpoint.
The script below writes replies to JSONL, saves the root tweet once, deduplicates by tweet_id, and stores page metadata for auditability.
1import json
2import time
3from datetime import datetime, timezone
4from pathlib import Path
5
6import requests
7
8TOKEN = "<your_bearer_token>"
9TWEET_ID = "<tweet_id>"
10SORT_BY = "Recency"
11URL = f"https://api.twexapi.io/twitter/tweets/{TWEET_ID}/replies/page"
12REPLIES_OUT = Path(f"{TWEET_ID}-replies.jsonl")
13ROOT_OUT = Path(f"{TWEET_ID}-root.json")
14META_OUT = Path(f"{TWEET_ID}-replies-meta.json")
15
16headers = {
17 "Authorization": f"Bearer {TOKEN}",
18 "Content-Type": "application/json",
19}
20
21cursor = None
22page_number = 0
23seen_reply_ids = set()
24page_log = []
25
26with REPLIES_OUT.open("w", encoding="utf-8") as replies_file:
27 while True:
28 payload = {"sort_by": SORT_BY}
29 if cursor:
30 payload["next_cursor"] = cursor
31
32 response = requests.post(URL, headers=headers, json=payload, timeout=30)
33 response.raise_for_status()
34 body = response.json()
35
36 page_number += 1
37
38 if page_number == 1 and body.get("root_tweet"):
39 ROOT_OUT.write_text(
40 json.dumps(body["root_tweet"], ensure_ascii=False, indent=2),
41 encoding="utf-8",
42 )
43
44 replies = body.get("data") or []
45 for reply in replies:
46 reply_id = reply.get("tweet_id") or reply.get("id")
47 if not reply_id or reply_id in seen_reply_ids:
48 continue
49 seen_reply_ids.add(reply_id)
50 replies_file.write(json.dumps(reply, ensure_ascii=False) + "\n")
51
52 page_log.append({
53 "page": page_number,
54 "items": len(replies),
55 "has_next_page": body.get("has_next_page"),
56 "next_cursor": body.get("next_cursor"),
57 })
58
59 if not body.get("has_next_page") or not body.get("next_cursor"):
60 break
61
62 cursor = body["next_cursor"]
63 time.sleep(1)
64
65META_OUT.write_text(json.dumps({
66 "tweet_id": TWEET_ID,
67 "sort_by": SORT_BY,
68 "exported_at": datetime.now(timezone.utc).isoformat(),
69 "unique_replies": len(seen_reply_ids),
70 "pages": page_log,
71}, ensure_ascii=False, indent=2), encoding="utf-8")
72
73print(f"Saved {len(seen_reply_ids)} replies to {REPLIES_OUT}")For scheduled jobs, persist the last successful cursor after each page. That makes failures recoverable without discarding the pages you already collected.
Fields Worth Keeping
Answer: Fields Worth Keeping means using TwexAPI Bearer APIs on api.twexapi.io for this user case. A typical read uses 5 Credits (about $0.05 per 1,000), and qualifying paid plans publish 20+ QPS. As of 2026-08-20, first-party developer API Post and User reads list at $5 and $10 per 1,000 resources; rate limits vary by endpoint.
At minimum, store:
- The raw reply object.
tweet_id,created_at, text fields, author fields, and interaction counts if present.in_reply_to,reply_to,conversation_id, or related thread fields when returned.- The root
tweet_id,sort_by, export time, page number, and cursor metadata. - A normalized reply URL such as
https://x.com/i/web/status/<reply_id>.
Keep raw data beside normalized rows. Reply schemas can evolve, and downstream analysis often needs fields you did not expect at export time.
Analysis Notes
Answer: Analysis Notes means using TwexAPI Bearer APIs on api.twexapi.io for this user case. A typical read uses 5 Credits (about $0.05 per 1,000), and qualifying paid plans publish 20+ QPS. As of 2026-08-20, first-party developer API Post and User reads list at $5 and $10 per 1,000 resources; rate limits vary by endpoint.
Reply exports are useful for:
- Measuring early product or campaign feedback.
- Reviewing customer concerns after an announcement.
- Building moderation queues around a specific post.
- Studying how discussion changes when sorted by recency versus likes.
- Sampling replies for manual labeling before sentiment or topic modeling.
Do not treat reply data as a complete public opinion poll. Replies are shaped by ranking, deletion, account visibility, and who chooses to respond. Store enough context so the limits of the dataset are visible.
Common Pitfalls
Answer: Common Pitfalls means using TwexAPI Bearer APIs on api.twexapi.io for this user case. A typical read uses 5 Credits (about $0.05 per 1,000), and qualifying paid plans publish 20+ QPS. As of 2026-08-20, first-party developer API Post and User reads list at $5 and $10 per 1,000 resources; rate limits vary by endpoint.
- Pulling only the first page and calling it the full conversation.
- Changing
sort_byhalfway through pagination. - Dropping
root_tweet, then losing the context for the reply dataset. - Running sentiment analysis without language detection or manual review.
- Overwriting interaction counts without a timestamp.
Wrap-up
Answer: Wrap-up means using TwexAPI Bearer APIs on api.twexapi.io for this user case. A typical read uses 5 Credits (about $0.05 per 1,000), and qualifying paid plans publish 20+ QPS. As of 2026-08-20, first-party developer API Post and User reads list at $5 and $10 per 1,000 resources; rate limits vary by endpoint.
For reply collection, use POST /twitter/tweets/{tweet_id}/replies/page, keep sort_by stable, continue with next_cursor, and save the root tweet plus raw reply rows. The result is easier to audit, retry, and explain than a single large fixed-count request.