Skip to main content
GET https://xquik.com/api/v1/x/tweets/{id}/retweeters
Requested result counts are upper bounds for paid authenticated calls. Remaining credits may not cover the full page or ID list. If so, Xquik returns fewer results. If zero paid results are affordable, it returns 402 insufficient_credits.
1 credit per result returned · All plans from $0.00012/credit · Supports guest paid reads
This route shows who retweeted one public tweet. The response returns one user profile per visible reposting account. The route is GET /api/v1/x/tweets/{id}/retweeters. A post X does not have returns 404 tweet_not_found, as Get tweet does. Deleted, suspended-account & protected posts count as missing. A post without reposts returns an empty page. A 404 costs no credits.
The Node.js and Python snippets write JSON Lines retweeter rows plus a separate checkpoint. They do not write raw response pages. Store each mapped row and the latest next_cursor. An import, giveaway verifier, CRM sync, or agent job can then resume. It can resume from the last completed page without duplicate rows.

Retweet timestamps

Set includeRetweetTimestamp=true to add each repost’s time. The option makes the call take longer.
Retweet timestamps
Read users[].retweetedAt as a UTC ISO 8601 timestamp or null. null means the lookup could not establish the matching repost time. The profile remains in the response when that lookup fails or expires. Neither the account creation date nor the original post date replaces it. createdAt continues to describe the account’s creation date. The option defaults to false. Ordinary retweeter responses omit retweetedAt. Keep it enabled on later pages when exporting timestamps. The Engagement Scraper accepts the same option for retweeters results. Its dataset rows use retweetedAt.

Direct retweeter handoff

Use GET /api/v1/x/tweets/{id}/retweeters when a workflow needs one row per account. Each row is an account that retweeted or reposted a tweet. Use these rows for giveaway checks, CRM imports, audience reviews, or follow-up jobs. Store source_tweet_id, retweeter_id, username, display_name, follower_count, following_count, verified, verified_type, and profile_image_url. Store next_cursor as a separate checkpoint.

Retweeter rows

Store users[] as the profile rows for accounts that reposted the source tweet.

Stable upserts

Store users[].id as retweeter_id with source_tweet_id for idempotent imports and giveaway checks.

Readable labels

Store users[].username and users[].name for handles, labels, and review queues.

Profile enrichment

Store description, location, url, and profilePicture when returned for CRM and warehouse enrichment.

Audience signals

Store followers, following, verified, and verifiedType for reach scoring, filters, and outreach priority.

Approved contact

Use DM endpoints only after a user-approved message flow. The write response tells you whether X delivered the DM.

Next page

Store has_next_page and next_cursor. Then pass next_cursor back as cursor only when has_next_page is true.

Credit-limited pages

Use users.length, not a requested page size, for row counts. Low balances can return fewer rows.
Direct retweeter reads cost 1 credit per user returned. Low credit balances can return fewer users than a full page. Zero affordable results return 402 insufficient_credits.

Retweeter questions

Can I see who retweeted my tweet?

Yes, for profiles visible to this endpoint. Pass the tweet’s numeric ID. The response lists handles, names, follower counts, and verification fields. Continue pagination only when the response confirms another page. X documents this read intent as Get Reposted by.

Why can’t I see every retweeter?

X controls which profiles each request exposes. Deleted, protected, blocked, or withheld accounts may not appear. X may also omit accounts it cannot return. Pagination and credit limits can shorten one page. A missing profile cannot confirm zero repost activity.

Do retweeters include quote tweets?

No. A standard repost shares the source tweet without added commentary. The quote-tweets endpoint returns added commentary. Use the tweet-replies endpoint to read the conversation.

How do I export retweeters?

The Node.js and Python examples write one JSON Lines row per user. Store the source tweet ID beside each profile. Use next_cursor to resume an interrupted export. Use toolType=repost_extractor for a saved CSV, JSON, or XLSX job.

How can I analyze retweeters?

Compare complete snapshots with numeric user IDs. Record the collection time beside follower and verification fields. A repost does not prove endorsement or a business relationship. Report only returned profile attributes.

Path parameters

Query parameters

Choose fields

Which tweet engagement endpoint?

Retweeters

Use GET /x/tweets/{id}/retweeters for user profiles that reposted one source tweet.

Tweet likers

Use GET /x/tweets/{id}/favoriters for user profiles that liked one source tweet.

Quote tweets

Use GET /x/tweets/{id}/quotes when you need tweet rows that quote the source tweet.

Tweet replies

Use GET /x/tweets/{id}/replies when you need reply tweet rows under the source tweet.

Saved exports

Use Create extraction with toolType=repost_extractor for a saved job or CSV, JSON, or XLSX export.

DM handoff

Use Send DM only after your workflow has a user-approved outreach step.

User result filters

These filters apply before billing. Selective filters can return fewer rows.See user filters for every filter. Common ones are minFollowers, verifiedOnly, hasWebsite, hasEmail, bioContains, and locationContains.

Headers

Response

200 OK

With enrichProfiles=true, each row carries the full profile. The x-xquik-profile-enrichment header then counts the rows that have it, as in enriched=180; requested=200. A row without it keeps its list fields.

400 Invalid input or cursor

{ "error": "invalid_cursor", "message": "Cursor invalid or expired. Start again without cursor, then use next_cursor." } A cursor X can’t read returns invalid_cursor. Start again without cursor, then use next_cursor. Other invalid input returns invalid_input. Both answers are free.

401 Unauthenticated

Anonymous requests receive WWW-Authenticate: Bearer. This is not a Payment challenge.

402 Payment required

Account keys receive account options. A guest wallet receives a checkout option. Confirm any payment action.

Response examples

200 example

  • 400 { "error": "invalid_input", "message": "Invalid input. Check the request body." }
  • 401 { "error": "unauthenticated", "message": "Authentication required." }
  • 402 { "error": "insufficient_credits", "message": "Insufficient credits. Top up or subscribe to continue." }
  • 403 { "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." }
  • 404 { "error": "tweet_not_found", "message": "Tweet not found. Check the tweet ID." }
  • 424 { "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." }
  • 429 { "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }
  • 502 { "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." }
  • 503 { "error": "x_api_unavailable", "message": "Xquik is busy right now. Retry shortly." }