The request body accepts the same fields as Create Extraction, including all 16 tweet search filter parameters. Only toolType and the corresponding target field are required for the estimate.
Maximum number of results to extract. When set, the estimate caps estimatedResults to this value and adjusts projected usage accordingly. Useful for previewing the cost of a partial extraction.
Request body is missing or malformed. Ensure toolType and the corresponding target field are present.
{ "error": "invalid_tool_type" }
The toolType value is not one of the 20 supported tools.
{ "error": "unauthenticated" }
Missing or invalid API key.
{ "error": "no_subscription" }
No active subscription, or the monthly usage limit has been reached. Possible error values: no_subscription, subscription_inactive, usage_limit_reached.
{ "error": "tweet_not_found", "message": "Tweet not found" }
The target tweet does not exist, was deleted, or the ID is invalid.
{ "error": "user_not_found", "message": "X user not found" }
The target user does not exist or is suspended.
Always call this endpoint before running an extraction to avoid hitting usage limits. If allowed is false, the corresponding Create Extraction request will return a 402 error. Check your current usage on the dashboard.