Twitter tweet JSON: fields, format and a real response
What a Twitter tweet JSON object looks like: a real recorded response, what every field means, how to get a feed as JSON and how it compares to Reddit JSON.
Piyushh · November 13, 2026 · 3 min read

A Twitter tweet JSON object is a flat record with an id, the text, a timestamp, engagement counts, a few flags and an author object. The sample below is a real response recorded with a test key on 2026-10-14, trimmed to the fields that matter. Below it you'll find a field-by-field guide, the call that produced the sample, and what to do when you want a whole feed instead of one tweet.
A real tweet as JSON
This is GET /v1/x/tweets/2099495333231288346, the tweet lookup endpoint:
{
"data": {
"id": "2099495333231288346",
"text": "meta ads: how important is the “connect to your crm” recommendation? ...",
"url": "https://x.com/HesomParhizkar/status/2099495333231288346",
"createdAt": "2026-09-14T13:47:48.000Z",
"lang": "en",
"likes": 2,
"retweets": 0,
"replies": 2,
"quotes": 0,
"views": 139,
"bookmarks": 0,
"isReply": false,
"inReplyToId": null,
"conversationId": "2099495333231288346",
"isRetweet": false,
"quotedTweetId": null,
"isQuote": false,
"hasVideo": false,
"urls": [],
"mentions": [],
"author": {
"id": "35363135",
"handle": "HesomParhizkar",
"name": "Hesom",
"followers": 584,
"following": 2010,
"verified": false,
"blueVerified": true,
"canDm": true,
"createdAt": "2009-04-26T01:18:19.000Z"
},
"media": [],
"quotedTweet": null,
"retweetedTweet": null
}
}
Whatever you send, a test key returns one recorded real response per endpoint, for free. A live key returns the live tweet, and that response also carries credits and requestId next to data. I cut a few fields (the bio, avatar and banner URLs) to save space.
What each Twitter JSON field means
| Field | Meaning |
|---|---|
id | The tweet's id, as a string. Keep it a string. |
text | The full text. |
url | The link to the tweet on x.com. |
createdAt | When it was posted, in UTC, ISO 8601. |
lang | The language code X detected. |
likes, retweets, replies, quotes, bookmarks | Engagement counts at the time of the call. |
views | The view count at the time of the call. It was 138 on a search two calls earlier and 139 here, so it moves. |
isReply, inReplyToId | Whether it replies to another tweet, and which one. |
conversationId | The id of the first tweet in the thread. Use it to fetch the discussion. |
isRetweet, retweetedTweet | Whether it is a retweet, and the original. |
isQuote, quotedTweetId, quotedTweet | Whether it quotes another tweet, and which. |
urls, mentions, media | Links, mentioned accounts and attachments. Empty lists when there are none. |
author | The profile of whoever wrote it, inline. |
Look at the author block. Some APIs give you only an author id, and you have to join a second object to get the rest. Here the handle, follower count and canDm come back in the same response, so most jobs need just one call.
Get a Twitter feed as JSON
A feed is a list. Use the timeline endpoint for an account, or search for a keyword:
# one account's recent tweets, newest first
curl -s "https://api.chatterapi.com/v1/x/users/levelsio/tweets" \
-H "Authorization: Bearer $CHATTERAPI_KEY"
# tweets matching a query
curl -s "https://api.chatterapi.com/v1/x/tweets/search?q=crm%20recommendation&sort=latest" \
-H "Authorization: Bearer $CHATTERAPI_KEY"
Both return the same envelope: data as a list of tweet objects like the one above, a page with nextCursor and hasMore, and credits. A page holds about 20 tweets and costs 2 credits on a live key. To get the next page, pass page.nextCursor back as cursor. In practice, a Twitter JSON feed is a loop over pages.
This is polling, and there is no push stream. If you came for a live one, read Twitter streaming API.
Parse it in code
import os, requests
r = requests.get(
"https://api.chatterapi.com/v1/x/tweets/2099495333231288346",
headers={"Authorization": f"Bearer {os.environ['CHATTERAPI_KEY']}"},
timeout=30,
)
t = r.json()["data"]
print(t["createdAt"], "@" + t["author"]["handle"], t["likes"], "likes")
Nullable fields can come back null, so handle that case in your code. In the sample, inReplyToId, quotedTweetId and the two nested tweets are null.
Old URLs and other formats
Some tutorials point to URLs like search.twitter.com/search.json for a Twitter search JSON feed. Those belong to an older API generation. I haven't tested them, and I wouldn't build on them. The current X API uses api.x.com/2/... paths and returns a different shape; authors, for example, come back in an includes block. If you're working with X's own API, see Twitter API v2 and Python and the Twitter API.
Every parameter for the lookup endpoint is listed on its docs page: tweet lookup.
Reddit JSON works the same way
The same envelope also returns Reddit posts and threads, where a post carries a title, score and subreddit in place of likes and views. For that side, read Reddit JSON API and the docs for one Reddit post.
Fetch one yourself
Try the free X tweet lookup tool to fetch one tweet as JSON: paste a tweet URL and you get the same fields. To use it from a script, sign up with Google. The 7-day free trial includes 1,000 credits, enough for 500 tweet lookups. Plans are on the pricing page.