Skip to main content
The X API uses version numbers in endpoint paths to provide stability while allowing for evolution. Understanding our versioning strategy helps you plan integrations and stay current.

Current versions

VersionStatusDescription
v2CurrentModern endpoints, flexible pricing, all new features
v1.1LegacyLimited support, minimal updates
EnterpriseAvailableHigh-volume access with dedicated support
Use X API v2 for all new projects. This is where all new features ship.

Version in URLs

The version number appears in the endpoint path:
https://api.x.com/2/tweets
                   ^
                   version

Breaking vs. non-breaking changes

Breaking changes (require code updates)

These changes only occur in major version bumps:
  • Removing an endpoint
  • Removing a response field
  • Removing a query parameter
  • Adding a new required parameter
  • Changing a field’s data type
  • Renaming a field or resource
  • Changing response codes or error types
  • Modifying authorization scopes

Non-breaking changes (additive)

These can happen at any time without version changes:
  • Adding a new endpoint
  • Adding a new optional parameter
  • Adding a new response field
  • Adding new OAuth scopes
  • Changing error message text
  • Nulling fields for privacy/security reasons

Release schedule

TypeFrequencyNotice
Major versionsNo more than annuallyMigration guides provided
Non-breaking changesOngoingChangelog updates
Security patchesAs neededMay be applied to current version

Deprecation policy

When we release a new major version:
  1. Deprecation: Previous version is marked deprecated
  2. Support period: Deprecated version continues to work for a defined period
  3. Retirement: Deprecated version is removed

Definitions

StatusMeaning
ActiveFully supported with new features and fixes
DeprecatedNo new features; critical bugs only; use discouraged
RetiredNo longer accessible

Staying informed

Get notified about changes:

Migration resources

When a new version is released, we provide:
  • Migration guides: Step-by-step upgrade instructions
  • Endpoint mapping: v1 to v2 equivalents
  • Data format changes: Object model differences

Best practices

Use v2

Start new projects on the latest version.

Monitor announcements

Subscribe to changelog and forum updates.

Test changes

Test in development before production updates.

Plan migrations

Don’t wait until deprecation to upgrade.