Twitter Analytics API: Pull X Metrics as JSON

A Twitter analytics API is a REST interface that returns the raw measurement fields behind X activity as structured JSON: per-post like, repost, reply, quote and bookmark counts, account-level follower and post counters, and the post history you aggregate over. It is not a dashboard. It hands you the numbers so you can build your own reporting, alerting, or model input. TwitterAPIs exposes these fields across nine read endpoints on one Bearer key at $0.0008 per call, with no X developer account and no monthly plan.

Pull the corpus, then score it yourself. Use GET /twitter/tweet/advanced_search for a keyword or brand query, or GET /twitter/tweet/replies to read the replies under a specific post. Both return full post text, the author, the timestamp and the engagement counts as JSON. Feed that text into whichever classifier you already use, whether that is a hosted language model, a fine-tuned model, or a lexicon. We deliberately do not ship a sentiment score, because a number with no visible model behind it is not something you can defend to a client.

That is the common pattern. Poll GET /twitter/user/mentions for named-account monitoring and GET /twitter/tweet/advanced_search for unbranded keyword coverage, store a since_id or the newest post ID between runs so each poll is incremental, then run your own classification and alerting over the result. Because billing is per call rather than per seat, the cost tracks how often you poll and how wide your keyword set is, which makes the unit economics of a listening product predictable before you write the first line of it.

No. There is no developer application, no app review, and no OAuth flow to complete. You sign up, receive one Bearer token, and send it on every request. Signup includes $0.50 in free credit with no card on file, which covers several hundred metric calls before you decide whether to add funds.

Yes, for everything that is public. Engagement counts on any public post, any public account's follower and post counters, and any public account's post history are all readable with a plain GET. What you cannot get anywhere, from us or any other vendor, is the owner-only telemetry X keeps in its own analytics surface: impressions, profile visits, and link click counts for an account you control. Those never leave X's first-party products, so treat any vendor claiming to supply them as a red flag.

Every standard read is a flat $0.0008 per call. Post and search calls return roughly 20 records, which works out to about $0.04 per 1,000 posts including their metrics. The one exception is GET /twitter/user/tweets/complete at $0.0024, which walks an entire account archive in a single job instead of making you page through it. There is no monthly minimum and no plan tier, so a one-off analysis of a few thousand posts costs cents rather than a subscription.

GET /twitter/user/tweets/complete walks an account's full public archive rather than the recent window, so a multi-year backfill is a single job at $0.0024. For keyword-based history, GET /twitter/tweet/advanced_search accepts the same date operators the X search UI uses, so you can bound a query to any past window and page through the matches at $0.0008 per call.