Tweet JSON viewer

It's the raw JSON response from X's public syndication endpoint (cdn.syndication.twimg.com/tweet-result), the same source that powers embedded tweets on third-party websites. No API key, no developer account, no OAuth flow. You paste a tweet URL, our server forwards the request to X (the browser can't call X directly because of CORS), and you see exactly what X returned, with no schema validation, normalization, or field stripping on our end.

The official v2 API requires a paid developer plan, app credentials, OAuth, and per-endpoint rate limits, and the free tier was killed in 2023. The syndication endpoint is the public surface used by oEmbed-style embeds. It's free and unauthenticated, but read-only and limited to a single tweet at a time. You won't get private fields, your own timeline, search, or write access, just the public view of one post.

An array of attached media objects: photos, videos, and animated GIFs. Photos have media_url_https and original_info dimensions. Videos and GIFs have a video_info.variants array with each available bitrate and content_type. That's where you'd pull a direct .mp4 URL from. Type discriminates between 'photo', 'video', and 'animated_gif'.

Parsed structural elements of the tweet text: urls (with both the t.co shortened url and the expanded_url it points to), hashtags, user_mentions, and symbols ($TICKER cashtags). Each entry includes indices, the [start, end] character offsets in the raw text field. Use these to highlight or linkify the tweet client-side without re-parsing.

Technically yes, the endpoint is public and unauthenticated. Practically, treat it as best-effort. There's no documented contract, no SLA, and no published rate limits. Heavy or automated polling will get you blocked at the IP or fingerprint level. For a production app, cache aggressively, never call it from a tight loop, and have a fallback path for 404 (deleted), 403 (protected), and 429 (rate limited).

Reply tweets include a parent object. Quote tweets include a quoted_tweet. Polls, edits, community notes, long-form (Premium) posts, and threaded replies all add their own fields. X also iterates this response shape silently. Fields appear and disappear without notice. That's why this tool shows the raw JSON instead of a typed view: it's the honest answer to 'what's actually in there'.