General Labs technical FAQs

The endpoints we release in Labs will be previews and are likely to change before they are released broadly, so we encourage you to take that into consideration as you build. Before getting started, we encourage you to read more about Twitter Developer Labs.  

What is Twitter Developer Labs?

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

Where should I go if I’m experiencing an error or something unexpected with the Tweets and Users endpoints?

The first place you should go is to the Tweets and Users’ troubleshooting page. If you don’t find the answer there, please review the rest of the documentation on those endpoints. Next step would be to search our forums, and then submit a new topic to the forums if you can’t find a solution there.

Where can I leave feedback or request functionality related to the Labs endpoints?

Feedback is an important part of why we launched Labs. We are actively seeking feedback from all Labs participants about using Labs and the new Tweets and Users endpoints through this survey. Specifically, we are interested in hearing your feature requests, and your positive and negative experiences with the endpoints, data format, 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 welcome and encourage your feedback.


Do you have any code examples?

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. 

What is the OpenAPI specification, and why should I care?

The OpenAPI specification is an open standard that we are using it 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.

How do I authorize my request?

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:

Twitter OAuth 1.0a can be abstracted away using a tool such as twurl or an OAuth 1.0a auth library. Twurl does not work with OAuth2 at this point in time.

To simplify testing, we recommend using the app associated with your Twitter developer app and user-context credentials found on your designated Twitter developer app’s “Keys and tokens” page, including:

  • Consumer API keys
    • API key
    • API secret key
  • Access token and access token secret
    • Access token
    • Access token secret

See our guides for help understanding OAuth 1.0a and OAuth 2.

Can I use twurl to make requests to these endpoints?

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

Do you have any guides for beginners?

Yes! Please review our “Quick start” guides within our products section. We also recommend that beginners use Postman or Insomnia, two REST API development environments to explore the APIs before writing code.

Additional resources

  • Get started building with our quick start guides.
  • Check out our API reference to learn more about what’s available.
  • Give feedback on Twitter Developer Labs.
  • Tell us about your experience using the Twitter Developer Labs endpoints by filling out this survey.