Skip to main content
GET
Twitter Scraping Job History & Export Status API
Free - does not consume credits

Headers

string
required
Your API key. Session cookie authentication is also supported. Generate a key from the dashboard.

Query parameters

number
Number of extractions to return per page. Default: 50. Maximum: 100.
string
Filter by tool type. One of: article_extractor, community_extractor, community_moderator_explorer, community_post_extractor, community_search, favoriters, follower_explorer, following_explorer, list_follower_explorer, list_member_extractor, list_post_extractor, mention_extractor, people_search, post_extractor, quote_extractor, reply_extractor, repost_extractor, space_explorer, thread_extractor, tweet_search_extractor, user_likes, user_media, verified_follower_explorer.
string
Filter by job status. One of: completed, failed, running.
string
Cursor for pagination. Use the nextCursor value from the previous response to fetch the next page.

Response

200 OK

object[]
Array of extraction job summaries. Extraction object fields:
string
Unique extraction job ID.
string
Tool type used for this extraction.
string
Job status: completed, failed, or running.
number
Total number of extracted results.
string
ISO 8601 timestamp of when the job was created.
string
ISO 8601 timestamp of when the job finished. Only present for completed jobs.
boolean
Whether more results exist beyond this page.
string
Cursor for the next cursor parameter. Only present when hasMore is true.

401 Unauthenticated

Missing or invalid API key.

429 Rate Limited

Wait for the Retry-After value before making another request.

Pagination

Results are ordered by creation date (newest first). To iterate through all extractions:
  1. Make the initial request without the cursor parameter.
  2. Check hasMore. Pass nextCursor as the next cursor value.
  3. Repeat until hasMore is false.

Job inventory handoff

Use GET /extractions as the job inventory step before fetching details or exporting files. Treat nextCursor as opaque and pass it back as cursor; do not dump raw job lists into shared logs.

Page checkpoint

Store page_index, page_cursor, next_cursor, has_more, limit, tool_type_filter, and status_filter after each successful page.

Completed jobs

Store completed job id, toolType, totalResults, completedAt, detail_path, and export_path for the next fetch or file export.

Running or failed jobs

Keep status, createdAt, and id so dashboards can retry failed jobs or poll running jobs without rereading older pages.

Next API step

Use Get Extraction for paginated JSON rows, or Export Extraction for files.
Store page checkpoints separately from job rows:
Next steps: Get Extraction to retrieve full results for a specific job, or Create Extraction to run a new extraction.