Get Post Context and Available Replies
View all X (Twitter) Public Data API endpoints →Pass required id for a public tweet to request basic post information together with available replies. Optional cursor continues the returned discussion where supported. Keep the selected post's context separate from reply entries; this endpoint is not documented as an exhaustive author-written multi-post thread. Field names, pagination output and missing-post behavior have not been live-verified, so validate a successful sample before enforcing a conversation schema. Retain collection limits and omissions in any exported discussion.
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/tweet-thread API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/twitter/tweet-thread?key=<API_KEY>&id=<id>'
Query Result
Use Cases
- Build a discussion reader around a known public post, separating the root source from returned responses.
- Collect contextual exchanges under an announcement for qualitative research with explicit pagination and omission notes.
- Attach available discussion context to an editorial post citation without assuming a complete authored thread.
- Review a saved public conversation as a structured source record after validating root and reply field mappings.
Frequently asked questions
How can I request post context together with replies?
Supply required id for a public tweet, with optional cursor for available continuation. The catalog describes basic post information plus replies; validate the actual root-post, reply and pagination shapes before enforcing a conversation schema.
Does tweet-thread reconstruct a complete author-written thread?
That is not established. Available replies and basic context do not prove every response or all posts in an author's own multi-post thread. Keep root context separate from reply records and document omissions in exports.