Comparing Twitter API’s blocks endpoints

These guides will focus on the following areas:

  • API request parameters - The Twitter API v2 endpoint introduces a new set of request parameters. While some parameters will be familiar, especially for those integrating with Labs, there are many important differences such as the introduction of the fields and expansions parameters.
  • New JSON format - Twitter API v2 introduces a completely new JSON format. Any code that parses v1.1 standard, premium, and enterprise JSON payloads will need to be updated to work with the new formats.
  • App and Project requirements - To access the Twitter API v2, you will need to use credentials from a developer App that is associated with a Project

 

Blocks lookup

The v2 blocks lookup endpoint will replace the standard v1.1 GET blocks/list and GET blocks/ids endpoints.

The following tables compare the standard v1.1 and Twitter API v2 block endpoints:
 

Description Standard v1.1 Twitter API v2
HTTP methods supported GET GET
Host domain https://api.twitter.com https://api.twitter.com
Endpoint path

/1.1/blocks/ids.json

/1.1/blocks/list.json

/2/users/:id/blocking
Authentication OAuth 1.0a User Context OAuth 1.0a User Context
Default request rate limits 15 requests per 15 min (per user) 15 requests per 15 min (per user)
Data formats Standard v1.1 format

Twitter 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 Twitter API v2 format, please visit our data formats migration guide.

 

Manage blocks

The v2 manage blocks endpoints will replace the standard v1.1 POST blocks/create and POST blocks/destroy endpoints.

The following tables compare the standard v1.1 and Twitter API v2 block endpoints:

Block a user

Description Standard v1.1 Twitter API v2
HTTP methods supported POST POST
Host domain https://api.twitter.com https://api.twitter.com
Endpoint path /1.1/blocks/create.json /2/users/:id/blocking
Authentication OAuth 1.0a User Context OAuth 1.0a User Context
Default request rate limits None 50 requests per 15 min (per user)

 

Unblock a user

The following tables compare the standard v1.1 and Twitter API v2 unblock endpoints:

Description Standard v1.1 Twitter API v2
HTTP methods supported POST DELETE
Host domain https://api.twitter.com https://api.twitter.com
Endpoint path /1.1/blocks/destroy.json /2/users/:source_user_id/blocking/:target_user_id
Authentication OAuth 1.0a User Context OAuth 1.0a User Context
Default request rate limits None 50 requests per 15 min (per user)