Get Recent Replies to a Post
View all X (Twitter) Public Data API endpoints →Provide required id for the public post whose latest replies you want to inspect. Optional cursor requests another available reply page for that same post. This endpoint targets incoming replies to a particular post, not the replies authored by a selected username. No live sample established exact reply fields, response cursor keys, chronological ordering guarantees or unavailable-post behavior. Validate those shapes before strict parsing, and treat returned discussion as a bounded sample rather than every reply or a push stream.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/twitter/latest-replies API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/twitter/latest-replies?key=<API_KEY>&id=<id>'
Query Result
Use Cases
- Poll replies to a product announcement and route newly observed questions to a human support-review queue.
- Record discussion changes following a public launch using reply identifiers and timestamps once their fields are validated.
- Review recent responses to an institutional update for corrections that may merit an editorial follow-up.
- Build a bounded event-announcement reply sample for qualitative coding without claiming exhaustive audience feedback.
Frequently asked questions
What input selects the replies to a specific tweet?
Required id identifies the public post receiving replies; optional cursor requests another available page for that post. This is different from user-replies, which selects the author of outgoing replies with screenname.
Are all replies returned in guaranteed chronological order?
No exhaustive coverage or ordering guarantee was verified. Validate reply fields, output cursor keys and unavailable-post behavior before parsing. Repeated deliberate reads are bounded polling, not a push stream.