How fields work
By default, a post lookup returns onlyid, text, and edit_history_tweet_ids. To get more data, add field parameters to your request:
Available field parameters
Each object type has its own fields parameter:| Object | Parameter | Documentation |
|---|---|---|
| Post (Tweet) | tweet.fields | Post fields |
| User | user.fields | User fields |
| Media | media.fields | Media fields |
| Poll | poll.fields | Poll fields |
| Place | place.fields | Place fields |
Example: Post fields
Request specific post fields withtweet.fields:
Example: User fields
Request specific user fields withuser.fields:
Fields for related objects
To get fields on related objects (like the author of a post), you need two things:- An expansion to include the related object
- The fields parameter for that object type
Common field combinations
- Post analytics
- User profiles
- Full post context
- Media details
Important notes
- Field order in responses may differ from request order
- Missing fields in responses mean the value is
nullor empty - Some fields require specific authentication (e.g., private metrics need user context)
- Check each endpoint’s API reference for available fields
Next steps
Expansions
Include related objects in responses.
Data Dictionary
Complete field reference for all objects.