Comparing X API’s Posts lookup endpoints
The v2 Posts lookup endpoints will replace the standard v1.1 GET statuses/lookup and GET statuses/show endpoints, as well as the Labs Post lookup endpoints. If you have code, apps, or tools that use one of these versions of the Posts lookup endpoint, and are considering migrating to the newer X API v2 endpoint, then this set of guides is for you.
The following tables compare the various types of Posts lookup endpoints:
Description |
Standard v1.1 |
X API v2 |
HTTP methods supported |
GET |
GET |
Host domain |
https://api.twitter.com |
https://api.twitter.com |
Endpoint path |
/1.1/statuses/show.json /1.1/statuses/lookup.json |
/2/tweets |
OAuth 1.0a User Context |
OAuth 1.0a User Context OAuth 2.0 App-Only OAuth 2.0 Authorization Code with PKCE |
|
Post JSON format |
Standard v1.1 format |
X API v2 format (determined by fields and expansions request parameters, not backward-compatible with v1.1 formats) To learn more about how to migrate from the Standard v1.1 format to the X API v2 format, please visit our data formats migration guide. |
Supports selecting which fields return in the payload |
✔ |
|
| Supports the annotations fields | ✔ | |
| Supports requesting new metrics fields | ✔ | |
| Supports the conversation_id field | ✔ | |
| Provides Post edit history | ✔ | ✔ |
| Requires the use of credentials from a developer App associated with a Project | ✔ |