Comparing Labs search with other search endpoints

Before launching Twitter Developer Labs, Twitter already supported three tiers of search APIs: standard, premium, and enterprise. If you have some code, apps, or tools that you would like to port to Labs recent search, then this set of guides is for you. 

The updates you will need to make depends on your starting point. These guides will focus on the following areas:

  • Authentication - The Labs recent search endpoint supports OAuth 2.0 Bearer Token authentication. If you have been working with standard and premium endpoints using a bearer token, your code is likely ready for Labs. If you are using enterprise search, you will switch from Basic authentication to OAuth 2.0 Bearer Token authentication.
  • Supported HTTP request methods - Like the standard search endpoint, the Labs recent search endpoint supports only GET methods. Premium and enterprise search endpoints also support POST methods. 
  • API request parameters - The Labs recent search endpoint introduces a new set of request parameters. While some parameters may be the same as the other tiers, there are many important differences, such as timestamp formats. 
  • Query language - The query language and syntax supported by Labs recent search is shared by the premium and enterprise search endpoints. While there is a common set of operators, the ones available differ between Labs, premium and enterprise tiers. If you have been working with standard search you will need to write queries with a new language, although there are many similarities.
  • Tweet and User JSON - Twitter Developer Labs introduces a completely new design for encoding Tweet and User objects in JSON. Any code that parses standard, premium, and enterprise JSON payloads will need to be updated to work with the new Labs formats.
  • Response pagination metadata - All Twitter search APIs respond with metadata that enables you to navigate through multiple 'pages' of results, but the JSON key names are different. 
     

Depending on the search endpoint you are currently using, read about the details here:

To see a detailed comparison of search feature, see this table