Replies to a service-change announcement ask whether existing users are affected and when the change begins. Other comments repeat guesses. Before drafting an FAQ, establish which questions are present and which answers have evidence.
Use the original announcement as the scope
Retrieve the source with tweet_id and confirm that replies concern this change rather than an older notice. Extract the stated scope, timing and limits. Leave omitted policy details unknown; comments and AI-generated wording must not become substitutes for an actual decision.
Preserve both comment sampling routes
If using ordinary and latest-comment lookups, retain the entry point, time and cursor coverage. Deduplicate available identifiers and preserve links to the original post. Recent questions are useful but do not necessarily represent every reader's priorities. Describe partial collection as a sample.
Separate the question from its answer status
Rewrite a comment as a specific question, then mark it answered by the announcement, missing context or awaiting confirmation. A worksheet can contain source, question, evidence, answer owner and review requirement. Owners and statuses are your own assignments, not automatic API output. Strongly worded feedback may still contain a useful question.
Verify every draft answer
Combine repeated questions while keeping a source or confirmation record for each answer. AI may improve phrasing but must not decide service rules or promise timelines. Leave unresolved items pending. The endpoint does not publish or reply for you. Deliver a reviewable FAQ and open-question list for the responsible person to confirm before any separate publication step.
Requests used in this project
- Get comments:https://api.trmesh.com/openapi/api/v1/twitter/web/fetch_post_comments · Documentation
- Get the latest tweet comments:https://api.trmesh.com/openapi/api/v1/twitter/web/fetch_latest_post_comments · Documentation
- Get single tweet data:https://api.trmesh.com/openapi/api/v1/twitter/web/fetch_tweet_detail · Documentation
Request URL and parameters
GET https://api.trmesh.com/openapi/api/v1/twitter/web/fetch_post_comments
| Parameter | Type | Required | Meaning |
|---|---|---|---|
tweet_id |
string | Yes | Tweet ID |
cursor |
string | No | Cursor |
Run the Python example
Install requests and set TRMESH_API_TOKEN in your environment. Replace the sample identifiers with the public object you intend to inspect. Example IDs may no longer be available.
import os
import requests
# Read your own developer key from the server environment.
url = "https://api.trmesh.com/openapi/api/v1/twitter/web/fetch_post_comments"
params = {
"tweet_id": "1835124037934367098"
}
response = requests.get(
url, params=params, timeout=30,
headers={"Authorization": f"Bearer {os.environ['TRMESH_API_TOKEN']}"},
)
response.raise_for_status()
payload = response.json()
print(payload) # Inspect the actual response before mapping fields
Endpoint documentation · Free profile tool
API calls use your TRMesh account allowance. Check the endpoint price before running a script.