Blocks lookup: Standard v1.1 compared to Twitter API v2

If you have been working with the standard v1.1 GET blocks/ids and GET blocks/list endpoints, the goal of this guide is to help you understand the similarities and differences between the standard v1.1 and Twitter API v2 blocks lookup endpoints.

  • Similarities
    • Authentication
  • Differences
    • Endpoint URLs
    • Users per request limits
    • App and Project requirements
    • Request parameters
    • New JSON format

 

Similarities

Authentication

Both the standard v1.1 and Twitter API v2 blocks lookup endpoints use OAuth 1.0a User Context. Therefore, if you were previously using one of the standard v1.1 blocks lookup endpoints, you can continue using the same authentication method if you migrate to the Twitter API v2 version. 

 

Differences

Endpoint URLs

  • Standard v1.1 endpoints:
    • GET https://api.twitter.com/1.1/blocks/ids.json
      (list of user IDs who are blocked by the specified user)
    • GET https://api.twitter.com/1.1/blocks/lists.json
      (list of users who are blocked by the specified user)
  • Twitter API v2 endpoint:
    • GET https://api.twitter.com/2/users/:id/blocking
      (list of users who are blocked by the specified user ID)
       

Users per request limits

The standard v1.1 endpoints allow you to return up to 5000 users per request. The new v2 endpoints allow you to return up to 1000 users per request. To return a full 1000 users, you will need to pass max_results=1000 as a query parameter; you can then pass the next_token returned in the response payload to the pagination_token query parameter in your next request.
 

App and Project requirements

The Twitter API v2 endpoints require that you use credentials from a developer App that is associated with a Project when authenticating your requests. All Twitter API v1.1 endpoints can use credentials from standalone Apps or Apps associated with a project.

Request parameters

The following standard v1.1 request parameters accepted two request query parameters (user_id or screen_name). The Twitter API v2 only accepts the numerical user ID, and it must be passed as part of the endpoint path.

One of the biggest differences between standard v1.1 and Twitter API v2 endpoint versions is how you select which fields return in your payload. For the standard endpoints, there are several parameters that you could use to identify which fields or sets of fields would return in the payload, while the Twitter API v2 version simplifies these different parameters into fields and expansions
 

New JSON format

Twitter API v2 is introducing new JSON designs for the objects returned by the APIs, including Tweet and user objects.

  • At the JSON root level, the standard endpoints return user objects in a statuses array, while Twitter API v2 returns a data array. 
  • Instead of referring to Retweeted and Quoted "statuses", Twitter API v2 JSON refers to Retweeted and Quoted Tweets. Many legacy and deprecated fields, such as contributors and user.translator_type are being removed. 
  • Instead of using both favorites (in Tweet object) and favourites (in user object), Twitter API v2 uses the term like. 
  • Twitter is adopting the convention that JSON values with no value (for example, null) are not written to the payload. Tweet and user attributes are only included if they have non-null values.
     

In addition to the changes that we made to our new JSON format, we also introduced a new set of fields to the Tweet object including the following:

Was this document helpful?
Thank you

Thank you for the feedback. We’re really glad we could help!

Thank you for the feedback. How could we improve this document?
Thank you for the feedback. Your comments will help us improve our documents in the future.