# Twitter/X Tweet Details Scraper · URL or ID (`data-slayer/twitter-tweet-details`) Actor

Turn public X/Twitter post URLs or numeric tweet IDs into clean tweet, author, engagement, media, and entity records. Built for one-off checks and bounded batches up to 100 inputs.

- **URL**: https://apify.com/data-slayer/twitter-tweet-details.md
- **Developed by:** [Data Slayer](https://apify.com/data-slayer) (community)
- **Categories:** Social media, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.55 / 1,000 tweet details

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Twitter/X Tweet Details Scraper · URL or ID

Turn public X/Twitter post URLs or numeric tweet IDs into clean tweet, author, engagement, media, and entity records—one unique post per dataset row.

### Watch the demo

YouTube video coming soon.

### What this Actor does

Use this Actor when you already know the posts you need and want their current public details without running a broad search. It is designed for one-off checks, spreadsheet enrichment, webhook follow-ups, and bounded batches of up to 100 inputs.

For every available public post, the default dataset receives one normalized row with:

- post ID, canonical URL, text, timestamp, language, and conversation ID;
- reply, quote, repost, and sensitive-content flags;
- likes, replies, reposts, quotes, bookmarks, and views when available;
- author ID, username, display name, verification state, and profile image;
- attached media metadata; and
- hashtags, mentions, and expanded URLs.

Thread and reply expansion is intentionally not included. Use a replies/comments workflow when you need the surrounding conversation.

### Input

| Field | Type | Required | Default | Limits | Purpose |
| --- | --- | --- | --- | --- | --- |
| `tweetUrlsOrIds` | array of strings | yes | — | 1–100 entries; each ≤300 characters | Numeric tweet IDs or public `x.com` / `twitter.com` status URLs. Duplicate IDs are processed once. |
| `maxInputs` | integer | no | `100` | 1–100 | Hard cap on unique inputs processed in the run. |

Valid input:

```json
{
  "tweetUrlsOrIds": [
    "https://x.com/NASA/status/1967659798526656877",
    "1967659798526656877"
  ],
  "maxInputs": 100
}
```

Supported URL forms include `x.com/<user>/status/<id>`, `twitter.com/<user>/status/<id>`, and `mobile.twitter.com/<user>/status/<id>`. Other domains and non-status URLs are rejected before any lookup.

### Output

Each available unique post creates one paid row in the default dataset.

| Field | Type | Nullable | Description |
| --- | --- | --- | --- |
| `tweetId` | string | no | Stable numeric post ID and dataset identity. |
| `url` | string | no | Canonical public post URL. |
| `text` | string | yes | Public post text. |
| `createdAt` | string | yes | Publication time as returned for the post. |
| `language` | string | yes | Language code when available. |
| `conversationId` | string | yes | Conversation root identifier when available. |
| `inReplyToTweetId` | string | yes | Parent post ID for a reply. |
| `isReply`, `isQuote`, `isRetweet`, `sensitive` | boolean | no | Post-type and sensitive-content flags. |
| `metrics` | object | no | Nullable integer counts for likes, replies, reposts, quotes, bookmarks, and views. |
| `author` | object | no | Nullable author ID, username, display name, verification state, and profile image URL. |
| `media` | array | no | Media type, URL, preview URL, dimensions, and duration when available. |
| `entities` | object | no | Hashtags, mentions, and expanded URLs. |
| `requestedInput` | string | no | The first submitted value that resolved to this unique post. |
| `retrievedAt` | string | no | UTC time when the row was normalized. |

Example:

```json
{
  "tweetId": "1967659798526656877",
  "url": "https://x.com/NASA/status/1967659798526656877",
  "text": "A sample public post used to illustrate the output contract.",
  "createdAt": "2026-09-15T14:30:00Z",
  "language": "en",
  "conversationId": "1967659798526656877",
  "inReplyToTweetId": null,
  "isReply": false,
  "isQuote": false,
  "isRetweet": false,
  "sensitive": false,
  "metrics": {
    "likeCount": 125,
    "replyCount": 9,
    "retweetCount": 21,
    "quoteCount": 4,
    "bookmarkCount": 7,
    "viewCount": 18420
  },
  "author": {
    "userId": "11348282",
    "username": "NASA",
    "name": "NASA",
    "verified": true,
    "profileImageUrl": "https://pbs.twimg.com/profile_images/example.jpg"
  },
  "media": [],
  "entities": {"hashtags": ["Space"], "mentions": [], "urls": []},
  "requestedInput": "https://x.com/NASA/status/1967659798526656877",
  "retrievedAt": "2026-09-21T00:00:00.000Z"
}
```

The example is illustrative and validates the proposed schema; it is not a live result claim.

### Empty, unavailable, partial, and failed runs

Invalid input stops before lookup. Deleted, private, missing, or otherwise unavailable posts do not become dataset rows and are not charged as tweet details. Their safe per-input outcomes remain in the free `RUN_SUMMARY` key-value record.

The summary distinguishes `succeeded`, `partial`, `empty`, `failed`, `charge_limit_reached`, `billing_uncertain`, and `cancelled`. It reconciles delivered and charged tweet rows. If the billing limit prevents a dataset push, no delivered row is counted. If a storage or billing response leaves the write outcome uncertain, the Actor stops and marks the state `billing_uncertain`; it does not retry or claim delivery for the possibly completed row. A response whose tweet ID differs from the requested ID is rejected before delivery or charging.

### Pricing

Pay per event. The Actor-start event is charged per GB of run memory, with a minimum of one event. The proposed 256 MB default therefore incurs one start event; choosing more than 1 GB can multiply it. A `tweet-detail` event is charged for each successfully delivered unique dataset row. Unavailable, invalid, failed, and duplicate inputs are not charged as tweet details.

| Plan | Actor start | Per tweet detail | 1 detail | 100 details |
| --- | ---: | ---: | ---: | ---: |
| Free | $0.0025 | $0.00075 | $0.00325 | $0.07750 |
| Bronze | $0.0023 | $0.00065 | $0.00295 | $0.06730 |
| Silver | $0.0021 | $0.00060 | $0.00270 | $0.06210 |
| Gold | $0.0020 | $0.00055 | $0.00255 | $0.05700 |
| Platinum | $0.0020 | $0.00055 | $0.00255 | $0.05700 |
| Diamond | $0.0020 | $0.00055 | $0.00255 | $0.05700 |

At the proposed 256 MB default, the input cap makes the maximum customer event charge for a 100-result run explicit. Increasing run memory above 1 GB can add start-event units. Platform compute usage, if any, is shown separately by Apify.

### Reliability and limits

- Transient rate-limit, server, and timeout failures use bounded retries and honor a short `Retry-After` value when provided.
- Requests are paced conservatively within a run. Coverage and freshness still depend on what is publicly available at lookup time.
- Duplicates are removed by tweet ID before lookup and again at delivery boundaries.
- No private posts, deleted posts, complete historical snapshots, or thread completeness are promised.
- Engagement counts can change after retrieval. Store `tweetId` as the stable join key and `retrievedAt` as the observation time.

### Use from the API

After publication, call the Actor with your Apify token:

```bash
curl "https://api.apify.com/v2/acts/data-slayer~twitter-tweet-details/runs?token=<YOUR_APIFY_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"tweetUrlsOrIds":["1967659798526656877"],"maxInputs":100}'
```

The proposed slug is not live yet. This endpoint becomes valid only after an authorized release.

### FAQ

**How much does it cost to run this Actor?**
Pricing is listed in the Pricing section above, charged per row returned. You only pay for the rows
the Actor actually produces, so a small test run costs cents.

**Do I need cookies or a login?**
No. This Actor reads public data only - no cookies, no account, no browser automation.

**Can I schedule it?**
Yes. Run it from the Apify API, on a schedule, or via a webhook, and export results as JSON, CSV or Excel.

**What if I need a slightly different output?**
Open an issue on the Actor's Issues tab describing the shape you need.

### Related actors

More Twitter actors from the same portfolio. Apify only auto-recommends actors in the same category, so here are the rest of ours:

| Actor |
|---|
| [Twitter/X Comments Scraper · No Cookies](https://apify.com/data-slayer/twitter-comments) |
| [Twitter/X Community Members Scraper · No Cookies](https://apify.com/data-slayer/twitter-community-members) |
| [Twitter/X Engaged Audience Exporter · Replies + Retweeters](https://apify.com/data-slayer/twitter-engaged-audience-exporter) |
| [Twitter/X Followers Scraper · No Cookies](https://apify.com/data-slayer/twitter-followers) |
| [Twitter/X Following Scraper · Public Profiles](https://apify.com/data-slayer/twitter-followings) |
| [Twitter/X List Members Scraper · No Cookies](https://apify.com/data-slayer/twitter-list-members) |
| [Twitter/X Profile Scraper · Bulk Handles, URLs & IDs](https://apify.com/data-slayer/twitter-user) |
| [Twitter/X Search Scraper · Small Jobs & Advanced Queries](https://apify.com/data-slayer/twitter-search) |
| [Twitter/X Trends Scraper · No Cookies](https://apify.com/data-slayer/twitter-trends-by-location) |
| [Twitter/X Tweets Scraper · No Cookies](https://apify.com/data-slayer/twitter-user-tweets) |

# Actor input Schema

## `tweetUrlsOrIds` (type: `array`):

Add 1–100 numeric tweet IDs or public x.com/twitter.com status URLs. Duplicate IDs are processed once.

## `maxInputs` (type: `integer`):

Hard safety cap after duplicate IDs are removed. Unavailable posts are included in this lookup cap but never saved as paid dataset rows.

## Actor input object example

```json
{
  "tweetUrlsOrIds": [
    "https://x.com/NASA/status/1967659798526656877"
  ],
  "maxInputs": 100
}
```

# Actor output Schema

## `results` (type: `string`):

One paid row per successfully resolved unique tweet.

## `runSummary` (type: `string`):

Free run outcome, counts, unavailable inputs, safe errors, and billing reconciliation.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "tweetUrlsOrIds": [
        "https://x.com/NASA/status/1967659798526656877"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("data-slayer/twitter-tweet-details").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "tweetUrlsOrIds": ["https://x.com/NASA/status/1967659798526656877"] }

# Run the Actor and wait for it to finish
run = client.actor("data-slayer/twitter-tweet-details").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "tweetUrlsOrIds": [
    "https://x.com/NASA/status/1967659798526656877"
  ]
}' |
apify call data-slayer/twitter-tweet-details --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,data-slayer/twitter-tweet-details"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/y0csEB5YCA4gaqN5S/builds/Yg9kMJDAdPM8jSgxd/openapi.json