Answers

Questions that come up while working with X data, answered in full. Several of them are about the official API and the answer is that it cannot do the thing; those say so.

Why is data.data undefined when I search the X API?Almost always because the query matched nothing. X omits the data key entirely on an empty result instead of sending an empty array, so read meta.result_count before you touch data.
How do I read tweets.data.data from twitter-api-v2?That is the raw current page held inside the paginator object. You usually want the paginator itself, which iterates every page for you, or its .tweets array for the page you are on.
How do I filter tweets by likes or retweets?You cannot on X API v2. The min_faves and min_retweets operators exist in the search syntax but are dropped for API callers, so the query runs without them and you get unfiltered results.
How do I measure engagement rate and reach on X?Engagement rate is (likes + retweets + replies + quotes) divided by impressions, times 100. Reach is the number of unique accounts that saw the post, which X does not publish, so it has to be estimated from impressions.
What is the cheapest way to pull X data at volume?Per-result credit pricing, and a query that filters on the provider side so you are not billed for rows you discard. The official X API v2 Basic tier is $200 a month for a fixed post cap.

Looking for something else

FAQ|API documentation|Ask us directly