# X Engagement Scraper | $0.15/1K | Pay-Per-Result (`xquik/x-engagement-scraper`) Actor

Scrape X (Twitter) replies, quotes, retweeters, likers, and threads for $0.15 per 1,000 delivered rows on every Apify plan. Process post URLs or IDs in bulk. Filters and deduplication run before billing. Apify bills platform usage separately. No X login. Built by Xquik. Not affiliated with X Corp.

- **URL**: https://apify.com/xquik/x-engagement-scraper.md
- **Developed by:** [Xquik](https://apify.com/xquik) (community)
- **Categories:** Social media, Lead generation, Automation
- **Stats:** 7 total users, 6 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.00015 / engagement rows

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

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## X Engagement Scraper | $0.15/1K | Pay-Per-Result

Collect Twitter engagement data for one or more X posts: replies, quotes,
retweeters, likers, and thread context. No X API key or login required.

### Replies, quotes, and profiles

- Post URLs and numeric Tweet IDs.
- Direct replies across available result pages.
- Direct and nested replies in 4 sort orders.
- Source post details as a selectable row.
- Quote posts with text, authors, media, and metrics.
- Retweeter and liker profiles.
- Conversation context around each source post.
- Multiple engagement types and posts per run.
- Global and per-resource caps.
- Source post and engagement-type attribution.
- Concurrent resources with saved cursor recovery.

### Input

```json
{
  "tweetIds": ["2082577277246972300"],
  "engagementTypes": ["replies", "quotes", "retweeters", "favoriters"],
  "maxItems": 10000
}
```

Keep `dedupeAcrossTargets` off to retain each source and engagement pairing.
Turn it on to keep one row per account across the run.

### Output

Rows use `tweet`, `replies`, `completeReplies`, `quotes`, `retweeters`,
`favoriters`, or `thread` as `resultType`. `sourceTarget` identifies the source
Tweet ID. Tweet and profile fields follow stable Xquik REST response shapes.

`completeReplies` preserves every returned row. The run report counts
`incompleteTargets` for partial coverage. Filters run before Actor billing.

### Pricing

Every Apify plan costs **$0.15 per 1,000 delivered rows**. Apify bills your
platform usage separately.

- One charge per delivered dataset row, including at most 1 zero-output
  diagnostic.
- No start, post, engagement-type, or page fee.
- Deduplication runs before billing.

Use `latest` unless you need an older build. Choose from 50 public tasks or 128
Xquik REST operations. Examples use sample values. Results reflect live data.

### Recovery and limits

Independent post-resource pairs run concurrently. Cursor lineage remains
ordered. Accepted rows, billing state, cursors, and fingerprints survive Apify
migration. The Actor has no self-imposed timeout.

Xquik is an independent third-party service. Not affiliated with X Corp.
"Twitter" and "X" are trademarks of X Corp.

# Actor input Schema

## `startUrls` (type: `array`):

Public x.com or twitter.com status URLs. Strings and {"url":"..."} objects are accepted.

## `tweetIds` (type: `array`):

Numeric Tweet IDs.

## `engagementTypes` (type: `array`):

Choose engagement resources. Replies, Quotes, Retweeters, and Likers run by default.

## `sort` (type: `string`):

Order complete reply rows. Other engagement types keep source order.

## `scope` (type: `string`):

Choose direct, nested, or all complete reply rows.

## `includeOriginalPost` (type: `boolean`):

Add the source post to complete reply results.

## `maxDepth` (type: `integer`):

Limit nested reply depth in complete reply results.

## `sinceTime` (type: `integer`):

Keep replies at or after this Unix timestamp in seconds.

## `untilTime` (type: `integer`):

Keep replies at or before this Unix timestamp in seconds.

## `language` (type: `string`):

Keep post rows with this language code.

## `mediaType` (type: `string`):

Keep post rows with the selected media type.

## `minViews` (type: `integer`):

Keep post rows with at least this many views.

## `minLikes` (type: `integer`):

Keep post rows with at least this many likes.

## `minReplies` (type: `integer`):

Keep post rows with at least this many replies.

## `minRetweets` (type: `integer`):

Keep post rows with at least this many reposts.

## `minQuotes` (type: `integer`):

Keep post rows with at least this many quotes.

## `minBookmarks` (type: `integer`):

Keep post rows with at least this many bookmarks.

## `verifiedOnly` (type: `boolean`):

Keep post authors or engagement profiles with verification.

## `maxItems` (type: `integer`):

Global cap across every post and selected engagement type.

## `maxItemsPerTarget` (type: `integer`):

Optional cap for each post and engagement type.

## `dedupeAcrossTargets` (type: `boolean`):

When off, the same account or post can appear once for each source post and engagement type.

## `maxConcurrency` (type: `integer`):

Parallel independent engagement reads. Leave the default for maximum safe throughput.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://x.com/OpenAI/status/2082577277246972300"
    }
  ],
  "engagementTypes": [
    "replies",
    "quotes",
    "retweeters",
    "favoriters"
  ],
  "sort": "relevance",
  "scope": "all",
  "includeOriginalPost": false,
  "verifiedOnly": false,
  "maxItems": 10000,
  "dedupeAcrossTargets": false,
  "maxConcurrency": 100
}
```

# Actor output Schema

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

Unique delivered rows. Filters and deduplication run before billing.

## `runReport` (type: `string`):

Outcome, reason, coverage completeness, counts, pages, duration, and privacy-safe anomalies.

# 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 = {
    "startUrls": [
        {
            "url": "https://x.com/OpenAI/status/2082577277246972300"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("xquik/x-engagement-scraper").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 = { "startUrls": [{ "url": "https://x.com/OpenAI/status/2082577277246972300" }] }

# Run the Actor and wait for it to finish
run = client.actor("xquik/x-engagement-scraper").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 '{
  "startUrls": [
    {
      "url": "https://x.com/OpenAI/status/2082577277246972300"
    }
  ]
}' |
apify call xquik/x-engagement-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,xquik/x-engagement-scraper"
        }
    }
}

```

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/bB9gzR3JDmTp5pnoz/builds/eZ924OJkTI0a7kbX6/openapi.json