How to get a tweet as JSON without an X API key
By Steven Van ·
Unif API tested FxTwitter, vxTwitter, X's syndication and oEmbed endpoints and its own free endpoint, all of which worked without a developer account.
You can read a single public X post as JSON without a developer account. Unif API published a test of five keyless options, run with curl on October 7, 2026 against one NASA post. All five returned HTTP 200 with no key, cookies or custom User-Agent.
What the five returned
- FxTwitter returns a JSON object (3.3 KB) with text, metrics, media URLs and the quoted post. Its user endpoint returns counts and the bio but no posts.
- vxTwitter returns a flatter object (1.6 KB) with the same essentials and a mediaURLs array.
- X's syndication endpoint returns the post as JSON (3.2 KB), but only likes and reply count, no reposts or views. It is undocumented, the token parameter has changed meaning before, and some posts come back as a stub instead of the text.
- X's oEmbed endpoint returns JSON wrapping an HTML blockquote, with no metrics or media URLs.
- UnifAPI's /tools/x/post returns the post with author, media, quoted post and every metric.
The UnifAPI endpoint
The endpoint is free with no login. The id parameter also accepts a full x.com or twitter.com status URL. Adding format=md or sending Accept: text/markdown returns the post as Markdown.
The post, author, metrics and media fields have the same shape on the search, replies, profile and media endpoints. Errors are typed, so a malformed id returns validation_error and a deleted post returns not_found. Protected accounts' posts also return not_found, since only public data is read.
Rate limits
Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. The free limit is 20 lookups per 10 minutes per visitor, and a search counts as two. A 429 response includes Retry-After and the URL where the limit is lifted, the metered X / Twitter API, which is pay as you go with no subscription. FxTwitter and vxTwitter run on volunteer infrastructure with no published rate limit.
Which to use
The post recommends FxTwitter for one post in a link-unfurling bot, and the syndication endpoint as a cross-check on what X serves. For a post that is the first step of a workflow that goes on to replies, search or timelines, it points to the free UnifAPI endpoints. For volume, history beyond the recent window or guarantees, it points to the metered API with a workspace key, which uses the same field names.
