GET https://xquik.com/api/v1/x/lists/{id}/tweets
Repost records include
retweetedAt, the repost event’s UTC ISO 8601 timestamp. It is null when
that timestamp is unavailable. The API omits it for original posts. The nested original post keeps
its own creation date. This field does not report every account that reposted a post. Request
per-account timestamps with Get retweeters.X (Twitter) list tweets questions
What does the Twitter lists API return?
The endpoint returns posts from accounts in one X List timeline. Each page can include Tweet text, author profiles, and timestamps. It can also include engagement counts, media, and pagination fields. The response represents one observed timeline window. It does not prove a complete archive or permanent List membership.How do I export tweets from an X (Twitter) list?
Request the first page with the numeric List ID. Normalize each Tweet into one row. Storehas_next_page beside next_cursor before requesting another page.
Use sinceTime and untilTime for a bounded collection window. Use
list_post_extractor for a saved CSV, JSON, or XLSX export.Why are some X (Twitter) list tweets missing?
First, checkincludeReplies. The default excludes replies. Then verify any
sinceTime and untilTime boundaries.
Visibility also depends on the connected read context. X says protected posts
remain visible only to approved followers. You cannot see private Lists that other
accounts own. Read X’s official Help with Lists
for current visibility rules.
Remaining credits can reduce a paid page. New posts can also shift a moving
timeline between requests. A missing Tweet does not prove deletion.Can this endpoint create or edit an X (Twitter) list?
No. This route only reads List tweets. It cannot create a public List or private List. It cannot add members, remove members, follow Lists, or publish posts. Use X’s Lists guide to create and manage Lists. Use the List Members endpoint for the current profile roster.How do I measure activity in a curated list timeline?
Group rows by stable author ID. Count Tweets, replies, reposts, likes, quotes, views, and media items separately. Store every count with its collection time. These measures describe captured List tweets. They do not expose unique viewers, link clicks, conversions, or audience sentiment.Does the API keep list tweet order?
Keep the returned Tweet sequence in every page. Do not treat that order as permanent. New posts and membership changes can shift later requests. Record collection time, List ID, and cursor with every page. Deduplicate retries by stable Tweet ID without re-ranking the saved rows.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 tweet returned · All plans from $0.00012/credit
next_cursor
row when has_next_page is true. Then pass it back as cursor for the next
page.Direct list tweet handoff
UseGET /x/lists/{id}/tweets when a caller
needs tweets from a curated X List. The caller can be a CRM, warehouse,
newsroom, monitoring job, or agent.
Store list_id, tweet_id, text, author_id, author_username,
author_name, author_followers, author_verified,
and created_at for each row. Also store author_profile_picture, engagement
counts, & media_urls for each row. Keep has_next_page & next_cursor with
the export checkpoint. The next run can then resume the list timeline without
duplicating earlier rows.
Use sinceTime & untilTime for bounded backfills. Set
includeReplies=true only when your queue needs reply tweets.List tweet rows
Store
tweets[] as timeline rows from accounts in the list. Use the row
shape above for newsroom, monitoring, CRM, and warehouse imports.Next page
Store
has_next_page and next_cursor. Only request another page when
has_next_page is true.Default page
Direct calls use the default paid tweet page size. The returned
tweets.length is the row count for this page.Time window
Use
sinceTime and untilTime for bounded backfills or repeat sync jobs.Reply filter
Leave
includeReplies unset to exclude replies. Set
includeReplies=true only when your queue needs reply tweets.Saved export
Use
list_post_extractor when the workflow needs a saved job. The
job has CSV, JSON, or XLSX output.Build a curated-list tweet feed
Use list tweets when a list ID defines the source accounts. Keep the list ID and collection time with every tweet. Save tweet ID, text, author, creation time, engagement counts, media URLs, and cursor. Keep the author ID because list membership can change later. Use this feed for research queues, newsroom monitoring, or account-group review. It represents tweets from curated list members, not tweets mentioning the list. Deduplicate pages by list ID and tweet ID. Store each page before advancing its cursor. New posts can shift the first page between runs. Use list members for the curated profile roster. Use list followers for the list’s audience. Use tweet search when keywords should define the result set.Path parameters
Query parameters
Tweet filters
Search operators such ascardName or near work on List posts too. You pay
only for rows that match your filters.See tweet filters for every filter. Common ones are fromUser, language, sinceDate, mediaType, minLikes, and hashtags.Choose fields
Which list endpoint?
List tweets
Use
GET /x/lists/{id}/tweets for tweets from accounts in the list.List members
Use
GET /x/lists/{id}/members for
accounts the list owner added to the list.List followers
Use
GET /x/lists/{id}/followers for
accounts that follow the list.Bulk list jobs
Use
Create extraction with
list_post_extractor, list_member_extractor, or list_follower_explorer
when the workflow needs a saved export.Headers
Response
200 OK
400 Invalid list ID
{ "error": "invalid_list_id", "message": "List ID required" }
The list ID path parameter is empty.401 Unauthenticated
Anonymous requests getWWW-Authenticate: Bearer and a guest wallet checkout action. This is not a Payment challenge.
Missing or invalid API key.402 Payment required
Account keys get account options. Guest keys get guest top-up only. No checkout starts automatically. Confirm any payment action.404 List not found
Xquik could not resolve the list. Check the list ID.502 X API unavailable
The read service returned an error. Retry after a short delay.429 Rate limit exceeded
You exceeded your tier rate limit. Wait for theRetry-After header before retrying.424 Dependency failed
The normalized v1 response contract can return 424 when the read service is unavailable.Related. List Members · List Followers
Response examples
- 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": "not_found", "message": "Resource not found." } - 409
{ "error": "coverage_cursor_unavailable", "message": "Cursor busy. Retry after the indicated delay." } - 410
{ "error": "coverage_cursor_gone", "message": "Cursor finished, expired, or superseded. Restart pagination without cursor." } - 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": "Maximum coverage is busy. Retry shortly." }