X Twitter Scraper

X Twitter scraper

Integrate Xquik as a third-party X data and automation API by selecting SDK, REST, Apify Actor, MCP, TweetClaw, or webhook patterns and preserving authentication, approval, pagination, and policy boundaries.

When to invoke

• "Search tweets or fetch tweet details with Xquik."
• "Export followers or following for an X account."
• "Run an Apify Actor for Twitter search results."
• "Verify Xquik webhook signatures."
• "Install TweetClaw for an OpenClaw X workflow."

Source checks

Before writing code, inspect the current Xquik source material. Do not invent endpoint names, request fields, response fields, scopes, pricing, limits, or package names.

Procedure

1. Identify the workflow: search, lookup, extraction, monitor, webhook, media, write action, billing, or MCP.
2. Choose the integration surface: generated SDK, REST, Apify Actors, MCP, TweetClaw, or webhooks.
3. Confirm authentication requirements from docs and keep API keys in environment variables or the existing secret manager.
4. Use typed request and response models when an SDK exists for the user's language.
5. Add retries and pagination according to SDK or API docs.
6. Ask for explicit user confirmation before write actions, payment flows, or long-running monitoring.
7. Verify HMAC signatures server-side before processing webhook business logic.
8. Return structured data instead of scraping generated UI output.

Integration surfaces

Apify Actor pattern

Start a bounded tweet run:

curl --fail --silent --show-error --request POST   "https://api.apify.com/v2/actors/xquik~x-tweet-scraper/runs"   --header "Authorization: ******"   --header "Content-Type: application/json"   --data '{"twitterHandles":["apify"],"outputVariant":"rich","maxItems":25}'

Start a bounded follower run:

curl --fail --silent --show-error --request POST   "https://api.apify.com/v2/actors/xquik~x-follower-scraper/runs"   --header "Authorization: ******"   --header "Content-Type: application/json"   --data '{"twitterHandles":["apify"],"relation":"followers","outputMode":"compact","maxItems":50}'

Record the returned run ID. Poll with bounded retries and stop on SUCCEEDED, FAILED, ABORTED, or TIMED-OUT. On success, read defaultDatasetId, then fetch dataset items. Treat maxItems as the whole-run cap, keep follower target metadata when attribution matters, treat resultType: "diagnostic" as status information, and inspect run-report rows before trusting incomplete results. Review live Apify pricing before every paid run because platform usage may apply separately.

Webhook and OpenClaw safety

Read the documented signing header name and payload format. Reject missing, malformed, or mismatched signatures. Store only fields needed for the product workflow.

Treat create, reply, quote, like, bookmark, retweet, follow, delete, media, and monitor actions as approval-worthy unless TweetClaw docs state a narrower policy. Keep read-only tweet search, reply search, profile lookup, follower export, and evidence collection low risk while respecting rate limits and account authorization. Use long-lived backend jobs for durable service workflows outside OpenClaw.

Safety and accuracy

• State that Xquik is a third-party X data and automation API.
• Do not claim affiliation with X Corp.
• Do not bypass access controls or platform policies.
• Do not expose API keys, webhook secrets, account cookies, tokens, or raw signatures.
• Do not hard-code credentials in examples or tests.
• Never put Apify API tokens in URL query parameters.
• Do not document private infrastructure details.
• Prefer official Xquik docs, SDK READMEs, and the OpenAPI spec over memory.
• Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.

Output template

## Xquik integration result — <workflow>

**Status:** implemented | plan only | blocked
**Surface:** SDK | REST | Apify Actor | MCP | TweetClaw | webhook
**Authentication:** environment variable | secret manager | not configured

| Requirement | Decision | Evidence | Risk control |
| --- | --- | --- | --- |
| Source docs | <docs read> | <URL> | <field or endpoint confirmed> |
| API call or actor | <endpoint, SDK method, or actor> | `<request shape>` | <pagination/retry/cap> |
| Secrets | <storage> | `APIFY_API_TOKEN` or other env var | <no logs/no URL token> |
| Approval | <needed or not> | <action type> | <confirmation or policy> |

### Validation
- <test, dry run, schema check, or webhook signature check>: pass | fail | not run

Quality gate

• Current Xquik docs, SDK README, OpenAPI spec, Actor page, MCP docs, or TweetClaw metadata were checked before naming fields or methods.
• API keys, webhook secrets, cookies, tokens, and signatures stay out of code, logs, URLs, and examples.
• APIFY_API_TOKEN is used for Apify authentication and never placed in a query string.
• Actor runs use bounded maxItems, bounded polling, and terminal status handling.
• Webhooks verify HMAC before parsing business logic.
• Write actions, payment flows, monitoring, media actions, and account-changing TweetClaw actions require explicit approval.
• The response states Xquik is independent and not affiliated with X Corp when relevant.

References

• REST API docs
• SDK index
• OpenAPI spec
• MCP server docs
• Skill repo
• TweetClaw OpenClaw plugin
• TweetClaw npm registry metadata
• X Tweet Scraper Actor
• X Follower Scraper Actor
• Tweet Actor run endpoint
• Follower Actor run endpoint