Interested in exploring Labs?
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.
Since Labs is an experimental program, the features and functionality of Labs products will likely evolve over time as we iterate development based on developer feedback. In some cases, changes made to Labs endpoints are not intended to be backward compatible. We will use versioning to avoid breaking changes to previously released versions and to allow for faster iteration. In such cases, we will plan to support prior versions for a period of time to allow for transitions to new versions.
Versioning for Labs endpoints will be represented within the endpoint URI by sequential version numbers containing a whole number for major revisions:
Breaking changes are those where a developer is expected to be forced to change their code. Examples of breaking changes include the following:
- Removing a field from a response
- Removing support for a query parameter
- Adding a required parameter
- Changing the type or semantic meaning of a field
Compatible changes are those that are not expected to break clients. Examples of compatible changes include the following:
- Adding a field to a response
- Adding support for an optional parameter
- Making a field value null when it wasn't before, if the specification for the field marked it as nullable.
Compatible changes may be made within a major version, and may be made with or without notice. Client applications should be built to tolerate these changes without breaking. All breaking changes to any Labs endpoints will be managed with releasing a new version for Labs endpoints at the same time, even if some endpoints are not affected by any breaking changes.
Generally, we expect that two versions of an endpoint will be maintained for a period of time to allow developers time to migrate without disruption to their application.
On February 25th, 2020, we announced that we were releasing a v2 version for the following endpoints:
We will retire the v1 versions of these endpoints on May 25th, 2020.