Twitter Developer Labs

With Twitter Developer Labs you can test new API previews, provide feedback, and get the latest news on what we're building.

Labs is available for developers with Elevated access.

Apply for Elevated access 

You can review the Twitter Developer error codes and troubleshooting page, where we have additional details on why you received an error. 

We have outlined a list of non-technical FAQs on the "About Labs" page that describes the Twitter Developer Labs program.

Please do not build production-level applications on Labs endpoints. The endpoints we release in Labs are previews of tools that may be released more broadly in the future, but will likely undergo changes before then. We encourage you to take that into consideration as you explore. Before getting started, please read more about Twitter Developer Labs. 

As we gather feedback and iterate on this API, we expect future versions to provide additional features. We would also appreciate feedback on new features introduced in Labs through our feedback channel.

If you are running into issues, please follow these steps:

1. Review our error codes page, where we have additional details on why you received that message. 
2. Review our FAQ pages which live in each endpoint section of our docs. 
3. Review the rest of the documentation on the endpoint that you are having difficulties with. 
4. Search our forums to see if someone else in the community has had a similar issue.
5. Submit a new topic to the forums if you can’t find a solution there.

Feedback is an important part of why we launched Labs. We are actively seeking feedback from all Labs participants through this survey or our feedback channel.

Specifically, we are interested in hearing your feature requests, and your positive and negative experiences with the endpoints, data formats, or general usefulness.

The Twitter Developer Labs team will be looking at your input for future iterations of Labs releases and the overall developer platform.

We put together a labs-sample-code repo on our @TwitterDev GitHub account. 

In addition to this, we have added a Run in Postman button to our "API reference" and "Quick start" pages. You can also download this API specification an upload it to other REST clients such as Insomnia if you prefer. 

The OpenAPI specification is an open standard that we are using to define the Twitter APIs. It’s useful for both humans and computers to discover what’s available in the API without needing to access it. It also defines what’s available in every API in Labs.

You will need an approved Twitter developer account, an activated Tweets and Users preview within the Labs portal, and a Twitter developer App assigned to that preview for you to be able to authorize a request to these endpoints.

You can access the endpoints using the following methods:

• OAuth 1.0a User Context - This method requires your Twitter developer App’s consumer key and secret, a set of generated access tokens, and a HMAC-SHA1 signature to make a successful request.
• OAuth 2.0 Bearer Token - This method requires a bearer token to make a successful request.

Twitter OAuth 1.0a can be tricky to use. We recommend using a tool such as twurl, Postman or Insomnia, or an OAuth 1.0a auth library to help auto-generate the signature required for a successful request.

Yes! Twurl is a great tool for making requests to Twitter APIs. We have included some example twurl requests in our API reference pages.