GETtweets

Bulk Fetch Multiple Tweets in One Request

Pass up to 100 tweet IDs and get full data for all of them in a single API call. Perfect for data pipelines, backfill jobs, and batch processing.

Average response time: 120ms

Code Examples

const ids = '1234567890,1234567891,1234567892';
const response = await fetch(
  `https://scrapebadger.com/v1/twitter/tweets/?tweets=${ids}`,
  { headers: { 'x-api-key': 'YOUR_API_KEY' } }
);
const tweets = await response.json();
console.log(`Fetched ${tweets.data.length} tweets`);
Response
{
  "data": [
    { "id": "1234567890", "text": "First tweet", "favorite_count": 42 },
    { "id": "1234567891", "text": "Second tweet", "favorite_count": 108 },
    { "id": "1234567892", "text": "Third tweet", "favorite_count": 7 }
  ]
}

API Reference

GET/v1/twitter/tweets/
ParameterTypeRequiredDescription
tweetsstringRequiredComma-separated list of tweet IDs (max 100)

Use Cases

Academic Research

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

Content Curation

Aggregate top-performing content by topic or industry to fuel newsletters, social feeds, and content marketing calendars.

Sentiment Analysis

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

Media Monitoring

Track how news stories propagate on Twitter, measure story amplification, and identify key distributors of information.

Market Research

Analyze consumer conversations, product feedback, and market trends to inform product development and go-to-market strategies.

Bot Detection

Identify automated accounts and inauthentic behavior by analyzing posting patterns, account metadata, and network structures.

Frequently Asked Questions

You can fetch up to 100 tweets per request by passing comma-separated IDs.

Valid tweets are returned normally. Invalid or deleted tweet IDs are silently skipped.

Batch requests use credits per tweet returned, same as individual calls. But you save on network overhead and latency.

No. Tweets are returned in the order they were created, regardless of the input order.