X Post Retweeters API

X Post Retweeters

Features

• Status URL resolutionAccept public x.com and twitter.com status URLs and resolve the numeric post identifier needed to collect the visible retweeter list.
• Normalized account profilesReturn profile ID, username, display name, canonical profile URL, biography, avatar, cover, and public account flags when available.
• Visible profile metricsCapture available follower, following, post, media, and like counts together with account creation and collection timestamps.
• Unique multi-post result setTraverse each submitted post with its own result cap, then save each normalized profile only once across the completed task.

Parameters

How to Use

Submit known public status URLs as an asynchronous task, poll its state, then page through the unique normalized profile results.

1. Prepare one or more public x.com or twitter.com URLs whose paths contain /status/{numeric_post_id}.
2. POST urls with a results_limit from 100 to 2,000 in increments of 100.
3. Poll /v1/tasks/{task_id} until the status is succeeded or failed.
4. Read /v1/tasks/{task_id}?limit=50 and pass results.next_cursor while results.has_more is true.

curl -X POST "https://api.socq.ai/v1/x/post-retweeters" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://x.com/OpenAI/status/1950240351547248941"],"results_limit":100}'

# Poll GET /v1/tasks/{task_id}
# Read GET /v1/tasks/{task_id}?limit=50 and follow data.results.next_cursor

Best Use Cases

• Amplification audience discovery: Build a unique directory of public accounts observed amplifying selected posts for research, review, or outreach preparation.
• Retweeter profile enrichment: Add canonical profiles, biographies, images, public account flags, locations, websites, and visible metrics to an amplification dataset.
• Cross-post audience overlap: Run one source post per task and compare stable profile IDs across completed result sets when per-post overlap or attribution matters.

Pro Tips

• Canonicalize status URLs and deduplicate by numeric post ID before batching because different URL forms for the same post are not guaranteed to collapse at input validation.
• Treat results_limit as a per-source-post cap, not a guaranteed result count; public visibility and available pagination can produce fewer profiles.
• Use one source URL per task when source attribution matters because normalized profile results do not retain the originating post URL or post ID.
• Follow the opaque task results.next_cursor independently from collection pagination; the public cursor pages through already saved normalized results.
• Use profile ID as the durable merge key across tasks and anchor changing public counters to collected_at.
• Allow nullable profile fields and empty results because public biographies, images, account signals, counters, or retweeter visibility may be unavailable.

Related APIs