GETtweets

Extract All Replies to Any Tweet

Get every reply to a tweet with full text, author profiles, and engagement data. Ideal for conversation analysis, customer feedback mining, and sentiment tracking.

Average response time: 90ms

Code Examples

const response = await fetch(
  'https://scrapebadger.com/v1/twitter/tweets/tweet/1234567890/replies',
  { headers: { 'x-api-key': 'YOUR_API_KEY' } }
);
const replies = await response.json();
replies.data.forEach(r => console.log(r.author.username, r.text));
Response
{
  "data": [
    {
      "id": "999001",
      "text": "Great feature! When will it be available?",
      "author": { "username": "curious_dev", "followers_count": 340 },
      "favorite_count": 5,
      "created_at": "2025-01-15T11:00:00Z"
    }
  ],
  "next_cursor": "reply_cursor_123"
}

API Reference

GET/v1/twitter/tweets/tweet/{tweet_id}/replies
ParameterTypeRequiredDescription
tweet_idstringRequiredThe tweet ID to get replies for
cursorstringOptionalPagination cursor for next page

Use Cases

Sentiment Analysis

Feed tweet text into NLP pipelines to classify sentiment, detect emotions, and measure public opinion on products, events, or topics.

Social Listening

Monitor brand mentions, keywords, and conversations across Twitter in real time to understand public sentiment and emerging topics.

Brand Monitoring

Get alerts when your brand is mentioned, track share of voice, and respond quickly to customer feedback or PR crises.

Crisis Monitoring

Detect and track PR crises, service outages, and negative viral moments in real time to enable rapid response.

Community Management

Manage Twitter communities by tracking member activity, top contributors, discussion themes, and community health metrics.

Academic Research

Collect large-scale Twitter datasets for computational social science, NLP research, political analysis, and network studies.

Frequently Asked Questions

Replies are returned in Twitter's default relevance order (a mix of engagement and recency). Use pagination to get all replies.

Yes. Each reply has its own tweet ID. Call this endpoint recursively to traverse full conversation trees.

Hidden replies are not included by default. Only publicly visible replies are returned.

ScrapeBadger has no per-endpoint rate limits. You can make up to 1,000 requests per second across all endpoints.