ABOUT
About TwitterAPIs
TwitterAPIs is an independent pay-per-call REST API for Twitter and X data, built and operated by a small team registered in Dubai. It serves 51 endpoints covering search, post detail, profiles, the follow graph, timelines, lists, trends and write actions, all authenticated with one Bearer header and billed per call rather than per plan. We are not affiliated with X Corp and we do not resell the official X API.
One price, no tiers
A standard read call is $0.0008 whether it is your first this month or your millionth. There is no plan to outgrow, no minimum to commit to, and no negotiation required to get a working price. Signup carries $0.50 of credit and no card.
The contract is published
Every endpoint is in a public OpenAPI 3.1 spec and a public reference. What the API serves and what the documentation says are checked against each other rather than maintained by hand in two places, because a spec that drifts from the server is worse than no spec.
Health is a public endpoint
The endpoint our own monitoring reads is reachable by anybody without a key. A provider that only lets you see the status it chooses to show you is asking for trust it has not earned.
A person answers
Support is a named contact with an email address and a Telegram handle, not a form that returns a ticket number. For an API that sits underneath somebody's production job, being able to reach a human on the day it breaks is part of the product.
What we build
One product, in three shapes. The REST API is the core: 37 read endpoints and 14 write actions behind a single key, documented in a public OpenAPI 3.1 spec. The MCP server wraps those same endpoints as tools an AI assistant can call directly, so an agent can read X data without anybody writing glue code. And the browser tools on this site put the two or three lookups people run most often behind a form, for the times when opening an editor is more effort than the question is worth.
What we do not build is a dashboard product, an analytics suite, or anything that competes with the things our customers build on top of us. The API is the whole product, which is why the pricing has one number in it.
Who to contact
Emma
Developer relations, TwitterAPIs
Emma is the named public contact for developer questions: endpoint behaviour, pricing, billing, integration help, and anything that looks like a defect. Questions arrive at emma@twitterapis.com or on Telegram, and both reach the same person.
For anything that is not a question, the changelog records what shipped and when, the status page reads the same public health endpoint our monitoring reads, the press page lists every registry and publication where TwitterAPIs appears with a link to each source, and the security page covers how keys and credentials are handled.
Frequently Asked Questions
TwitterAPIs is operated by a small team that builds and runs one product: a pay-per-call REST API for Twitter and X data. The company is registered in Dubai, and the public point of contact for developer questions is Emma, who handles developer relations and answers on Telegram and by email. There is no sales team to route around and no account manager gate on support.
The API serves 51 endpoints, 37 reads and 14 writes, on a pay-per-call model at $0.0008 for a standard read. There is no plan tier, no monthly minimum, and no seat count. Capacity is monitored continuously and the health endpoint that monitoring reads is public, so you can point your own uptime checks at the same signal we do.
Email emma@twitterapis.com or message the Telegram account linked from the contact page. Both reach the same person rather than a ticket queue. For a question that is really about the shape of an endpoint, the docs and the changelog usually answer faster, and both are linked from every page on this site.
No. TwitterAPIs is an independent third-party provider and is not affiliated with, endorsed by, or operated by X Corp. We are not a reseller of the official X API either. Using this API does not require an X developer account, and nothing here goes through the X developer console or its plan tiers.
An OpenAPI 3.1 specification, a full endpoint reference on the docs subdomain, a changelog of what shipped and when, a public health endpoint, a published MCP server on npm, and a markdown twin of every page on this site for machine readers. Those are the surfaces an integrator needs to evaluate a provider without asking anybody's permission first.
Calls are authenticated with a Bearer key over TLS. Where an endpoint acts on behalf of a logged-in account, you choose whether the session credential is passed per call and not retained, or registered once and held encrypted at rest. The privacy and data handling page states this in full, including what is logged for billing purposes, which is the call metadata needed to charge you correctly.