> ## Documentation Index
> Fetch the complete documentation index at: https://docs.x.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> Comprehensive changelog documenting every update to the X API v2, Enterprise APIs, Ads API, SDKs, streaming, compliance, webhooks, and developer platform tools.

To subscribe to updates, please [**“Turn on notifications”**](https://help.x.com/en/managing-your-account/notifications-on-mobile-devices#:~:text=In%20the%20top%20menu,%20you,you%20would%20like%20to%20receive) for [**@API**](https://x.com/api).

<Update label="Jun 3, 2025" description="X API">
  ### Change to DM Events Behavior

  Today, we made a change to X API V2 DM Events behavior. With the new change participant\_ids array will only be included for ParticipantsJoin and ParticipantsLeave events, and it will list only the participants who joined or left at the time of the event. The MessageCreate event will no longer include the participant\_ids array. Learn more [here](https://devcommunity.x.com/t/upcoming-change-to-x-api-dm-events-endpoints-behavior/241841).
</Update>

<Update label="May 20, 2025" description="X API">
  ### Launch of Account Activity API Endpoints

  Today, we launched new X API v2 [Account Activity API endpoints](/x-api/webhooks/introduction). Learn more [here](https://devcommunity.x.com/t/account-activity-api-is-now-available-in-v2/242895).
</Update>

<Update label="Apr 30, 2025" description="X API">
  ### Improvements to Media Upload Endpoint

  We made few improvements to media upload endpoint to improve the developer experience. We introduced Dedicated Endpoints for Chunked Media Upload [Media Upload endpoints](/x-api/media/introduction). Learn more [here](https://devcommunity.x.com/t/media-upload-endpoints-update-and-extended-migration-deadline/241818).
</Update>

<Update label="Apr 3, 2025" description="X API">
  ### Support for Email Address Retrieval with OAuth 2.0

  Today, we added support for email address retrieval with OAuth 2.0 in X API V2. Learn more [here](https://devcommunity.x.com/t/announcing-support-for-email-address-retrieval-with-oauth-2-0-in-the-x-api-v2/240555).
</Update>

<Update label="Feb 18, 2025" description="X API">
  ### Changes to User Affiliation Data

  Today, we made changes to X API V2 User Affiliation Data. With the new change affiliation.user\_id will return an array of user\_ids. Earlier it used to return a single user\_id as a string, even if a user had multiple affiliations. Learn more [here](https://devcommunity.x.com/t/change-to-x-api-user-affiliation-data/237164).
</Update>

<Update label="Jan 16, 2025" description="X API">
  ### Launch of Media Upload Endpoints

  Today, we launched new X API v2 [Media Upload endpoints](/x-api/media/introduction). Learn more [here](https://devcommunity.x.com/t/announcing-media-upload-endpoints-in-the-x-api-v2/234175/3).
</Update>

<Update label="Jan 13, 2025" description="Documentation">
  ### Launch of New Documentation Site

  Today, we launched our new X Developer Platform documentation site, [https://docs.x.com](https://docs.x.com).
</Update>

<Update label="Dec 17, 2024" description="X API">
  ### Launch of xurl Tool

  Today, we launched [xurl](https://github.com/xdevplatform/xurl), a new tool that simplifies API testing for X developers, which now supports OAuth 2.0.
</Update>

<Update label="Nov 22, 2024" description="X API v2">
  ### Addition of Community ID Tweet Field

  Today, we added the `community_id` Tweet Field to the X API v2. Learn more about it [here](https://x.com/tapshah21/status/1860061806653317126).
</Update>

<Update label="Sep 23, 2024" description="X API v2">
  ### Addition of DM Blocking Endpoints

  Today, we added the DM blocking and DM unblocking endpoints to the X API v2.
</Update>

<Update label="Aug 20, 2024" description="X API v2">
  ### Support for Longform Posts

  Today, we added the ability to create longform Posts with a length of 25k instead of 4k.
</Update>

<Update label="Aug 9, 2024" description="X API v2">
  ### Support for Long Form Posts

  Today, we added the ability to create long form Posts using the X API v2
</Update>

<Update label="Aug 2, 2024" description="X API v2">
  ### Retrieve User Affiliation

  Today, we added the ability to retrieve a User's affiliation programmatically using the X API v2
</Update>

<Update label="Jul 26, 2024" description="X API v2">
  ### Get Article Metadata

  Today, we added the ability to get Article metadata using the X API v2
</Update>

<Update label="Jun 17, 2024" description="X API v2">
  ### Get Profile Image and Cover Picture

  Today, we added the ability to get profile Image and cover picture URL via the X V2 API
</Update>

<Update label="Jan 16, 2024" description="X API v2">
  ### Addition of Connection Status Field

  Today, we added the connection\_status field in the X API v2. Learn more about it [here](https://devcommunity.x.com/t/announcing-connection-status-field-in-the-user-object-in-the-x-api-v2/212588).
</Update>

<Update label="Dec 12, 2023" description="X API v2">
  ### Addition of Trends Lookup Endpoint

  Today, we added the Trends lookup endpoint in the X API v2. Learn more about it [here](https://devcommunity.x.com/t/announcing-the-users-search-and-trends-lookup-endpoints-in-the-x-api-v2/210567).
</Update>

<Update label="Dec 8, 2023" description="X API v2">
  ### Addition of Users Search Endpoint

  Today, we added the Users Search endpoint in the X API v2. Learn more about it [here](https://devcommunity.x.com/t/announcing-the-users-search-and-trends-lookup-endpoints-in-the-x-api-v2/210567).
</Update>

<Update label="Nov 29, 2023" description="X API v2">
  ### Get DM Permissions

  Today, we added the ability to the get DM permissions via the X API v2. Learn more about it [here](https://devcommunity.x.com/t/dm-permissions-available-in-the-x-api-v2/209688).
</Update>

<Update label="Nov 20, 2023" description="X API v2">
  ### Launch of Subscription Type Field

  Today, we launched a subscription\_type field on the User object in the X API v2. Learn more about it [here](https://devcommunity.x.com/t/new-subscription-type-field-is-available-in-the-twitter-api-v2/209219/2).
</Update>

<Update label="Nov 2, 2023" description="X API v2">
  ### Get Posts Usage Endpoint

  Today, we launched an endpoint to programmatically get your posts usage in the X API v2. Learn more about it [here](https://developer.x.com/en/docs/twitter-api/usage/tweets/api-reference/get-usage-tweets).
</Update>

<Update label="Sep 28, 2023" description="X API v2">
  ### Launch of Reposts Lookup Endpoint

  Today, we launched an endpoint to lookup reposts of a post in the X API v2. Learn more about it [here](https://developer.x.com/en/docs/twitter-api/tweets/retweets/api-reference/get-tweets-id-retweets).
</Update>

<Update label="Sep 28, 2023" description="X API v1.1">
  ### Deprecation of Search Endpoints

  Today, we are deprecating the search/tweets, users/search, and geo/search endpoints in the X API v1.1. Learn more [here](https://developer.x.com/en/docs/twitter-api/enterprise/powertrack-api/guides/powertrack_recovery_and_redundancy_features).
</Update>

<Update label="Sep 21, 2023" description="X API: Enterprise">
  ### Deprecation of Replay API Endpoint

  Today, we are deprecating the Replay API endpoint from the enterprise X API. You can use [recovery](https://developer.x.com/en/docs/twitter-api/enterprise/powertrack-api/guides/powertrack_recovery_and_redundancy_features)  featured instead.
</Update>

<Update label="Aug 1, 2023" description="X API v1.1">
  ### Deprecation of Historical Powertrack Endpoints

  Today, we are deprecating the Historical Powertrack and Insights track endpoints from the enterprise X API.
</Update>

<Update label="Jun 26, 2023" description="X API v2">
  ### Removal of Follows Endpoints from Basic and Pro Tiers

  Today, we are removing the Follows and List Follows endpoints from the Basic and Pro tiers of the X API v2.
</Update>

<Update label="Jun 12, 2023" description="X API v2">
  ### Removal of Manage Blocks Endpoint

  Today, we are removing the Manage Blocks endpoint from X API v2.
</Update>

<Update label="May 31, 2023" description="X API v2">
  ### Support for Bookmarks Count and Long Posts

  Today, we added support for retrieving bookmarks count and the ability to retrieve posts with more than 280 characters in the X API v2.
</Update>

<Update label="Mar 14, 2023" description="X API v1.1">
  ### Deprecation of Statuses/Filter Endpoint

  Today, we are deprecating the statuses/filter endpoint in the X API v1.1 Developers can use the filtered stream endpoint in the X API v2.
</Update>

<Update label="Jan 5, 2023" description="X API v2">
  ### Support for View Counts

  Today, we are adding support for view counts in the X API v2. A new field called impression\_count is made available in the public\_metrics of the post payload.
</Update>

<Update label="Dec 21, 2022" description="X API v2">
  ### Addition of Verified Type Field

  Today, we are adding a verified\_type user field to the X API v2 that indicates the type of verification a user account has (blue, business, government or none) .
</Update>

<Update label="Dec 20, 2022" description="X API v2">
  ### Removal of Source Field

  Today, we are removing the source field from the post payload in the X APIs.
</Update>

<Update label="Oct 27, 2022" description="X API v2">
  ### Addition of Direct Messages Endpoints

  Today, Today, we are adding six v2 Direct Messages endpoints. This release includes three GET methods for retrieving Direct Message conversation events and three POST methods for creating new Direct Messages. These methods support group conversations for the first time.

  Please visit our [blog post](https://developer.x.com/en/blog/product-news/2022/new-v2-direct-messages-endpoints) to learn more about this update.
</Update>

<Update label="Sep 29, 2022" description="X API v2">
  ### Support for Edited Post Metadata

  Today, we are adding the ability for developers to retrieve edited post metadata using the X API v2.

  Please visit our [blog post](https://developer.x.com/en/blog/product-news/2022/supporting-edit-tweet-functionality) to learn more about this update.
</Update>

<Update label="Aug 3, 2022" description="X API v2">
  ### Addition of Filtering Operator Aliases

  Filtering/query operator "aliases" were added to search and filtered stream endpoints, across enterprise, premium, and v2. In many cases, the operator refers to posts instead of statuses, e.g. "in\_reply\_to\_tweet\_id" as an alias for "in\_reply\_to\_status\_id." In other cases, the new operator alias adds more clarity to the matching performed. For example., since posts can only have one video attachment, a new "has:video\_link" alias is provided for "has:videos." Check out the [v2 filtered stream operator table](https://developer.x.com/en/docs/twitter-api/tweets/filtered-stream/integrate/build-a-rule#list) to see more examples.
</Update>

<Update label="Jul 27, 2022" description="X API v2">
  ### Updates to Reverse Chronological Home Timeline

  Beginning today, the reverse chronological home timeline v2 endpoint can return every post created on a timeline over the last 7 days and the most recent 800 regardless of the creation date.
</Update>

<Update label="Jul 19, 2022" description="X API v2">
  ### New Filtering Operators for Filtered Stream

  Today, 10 new v2 filtering operators are now available to all developers building with the filtered stream endpoints, and another 10 are now more widely available.

  Please visit our [blog post](https://developer.x.com/en/blog/product-news/2022/twitter-api-v2-filtered-stream) to learn more about this update.
</Update>

<Update label="Jun 16, 2022" description="X API v2">
  ### Updates to Streaming Endpoints Latency

  Today, we’re making updates to the streaming endpoints in the X API v2 to reduce the latency by 50%.
</Update>

<Update label="May 23, 2022" description="X API v2">
  ### Enabling v1.1 Media Endpoints in Essential Access

  Today, we're enabling the v1.1 media endpoints in Essential access of the X API v2.

  Please visit our [forum announcement](https://devcommunity.x.com/t/v1-1-media-endpoints-available-for-essential-access-in-the-twitter-api-v2/171664) to learn more about this update.
</Update>

<Update label="May 19, 2022" description="X API v2">
  ### Launch of Reverse Chronological Home Timeline Endpoint

  Today, we’re launching a new endpoint that enables you to retrieve a collection of the most recent posts and reposts posted by who you follow.

  Please visit our [forum announcement](https://devcommunity.x.com/t/reverse-chronological-home-timeline-in-the-twitter-api-v2/171549) to learn more about this launch.

  Along with the new endpoints,  the variants field is now available for the [media object](https://developer.x.com/en/docs/twitter-api/data-dictionary/object-model/media). This will give you the type of content attached with the URL.
</Update>

<Update label="Mar 24, 2022" description="X API v2">
  ### Launch of Bookmarks Endpoints

  Today, we’re launching new endpoints that enable you to manage and lookup Bookmarks using the X API v2. The Bookmarks feature has long been available in the X app, but until now, there hasn’t been an endpoint that allows you to retrieve, create or build solutions to manage your Bookmarks via the API.

  Please visit our [forum announcement](https://devcommunity.x.com/t/build-with-bookmarks-on-the-twitter-api-v2/168804) to learn more about this launch.
</Update>

<Update label="Mar 17, 2022" description="X API v2">
  ### Launch of Quotes Lookup Endpoint

  Today, we’re launching the [quotes lookup endpoint](https://developer.x.com/en/docs/twitter-api/tweets/retweets/introduction) that lets you get the quotes for a post ID.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/introducing-the-quote-tweets-lookup-endpoint-to-the-twitter-api-v2/168370) to learn more about this launch.
</Update>

<Update label="Feb 3, 2022" description="Documentation">
  ### Updates to Documentation Navigation

  We’ve heard your feedback. Finding content in our documentation could be difficult, and it was confusing when you clicked on a link and were taken to an entirely different side navigation.

  Today, we’ve released an updated docs navigation that enables you to browse the full offering of the X Developer Platform from a single side navigation. With this launch, we eliminated redundant pages, removed confusing icons, and improved how you can interact with the different elements within the navigation.

  If you have any feedback, please let us know via our [feedback channel](https://twitterdevfeedback.uservoice.com/forums/930250-twitter-api).
</Update>

<Update label="Jan 20, 2022" description="X API v2">
  ### Improvements to Reposts and Likes Lookup Endpoints

  Today, we’re launching improvements to the [reposts lookup](https://developer.x.com/en/docs/twitter-api/tweets/retweets/introduction) and the [Likes lookup](https://developer.x.com/en/docs/twitter-api/tweets/likes/introduction) endpoints, allowing you to get back the complete list of accounts who have Liked or reposted a post, not just the last 100 accounts to do so.

  To learn more about this launch, please visit our forum announcement to learn more about this launch.
</Update>

<Update label="Dec 14, 2021" description="X API v2: Authentication">
  ### Support for OAuth 2.0 Authentication

  Today, all developers can now authenticate using OAuth 2.0 by selecting OAuth 2.0 as an authentication method in the Developer Console. We’ve added support for confidential and public clients and all relevant v2 endpoints to use this authentication method as part of this release.

  OAuth 2.0 is an industry-standard authorization protocol that provides developers more control over an application’s scopes and improves authorization flows across multiple devices. In other words, developers building applications for people on X will have more control over the information their App requests from its users, so that you only have to ask your end-users for the data and information you need.

  This modern authorization protocol will allow you to present your end-users with a more streamlined consent flow for authorizing your app, which only displays the specific scopes you have requested from them.

  To learn more about this launch, please visit our forum announcement.
</Update>

<Update label="Nov 15, 2021" description="X API v2: Early Access">
  ### Major Platform Updates to X API v2

  **Major platform updates: X API v2 is now the primary version, new Essential and Elevated access, and Policy changes**

  Today, we are announcing that X API v2 is now the primary version of the X API. We have launched enough endpoints and functionality into X API v2 to satisfy the needs of 90% of all existing Apps built on the X API.

  We are launching the following changes today to further improve upon the X API v2 developer experience:

  * Fast and free Essential access to the API, and free Elevated access to developers who have had their use cases approved. We have a lot more details on these access levels available on our About the X API page.

  * We are removing language in our Developer Policy that restricted how you build with X’s core features, and limited the number of users you can support through your app.

    * We are opening up our platform to encourage you to build tools and products that make X better, healthier, and extend the public conversation. [See a list of solutions we’d love to see you build](https://developer.x.com/en/docs/twitter-api/what-to-build).

    * Specifically, we’ve removed terms that restricted replication of the X experience, including X’s core features as well as terms that required permission to have high numbers of user tokens.

    * We know that building solutions that help people on X often means a developer has to build (or replicate) some of the things that are available on X. These changes to our Developer Policy are intended to drive clarity for the developer ecosystem and provide an open API platform that makes it easier for developers to build, innovate, and make an impact on the public conversation.

  We go into a lot more detail on this launch and the X API launches that led to this moment in our [forum post](https://devcommunity.x.com/t/ushering-in-a-new-era-for-the-twitter-developer-platform-with-the-twitter-api-v2/162087).

  In addition to exploring earlier changelog entries, we’ve put together some key resources that you can review to understand what all has released to X API v2 to-date:

  * [X API endpoint map](/x-api/migrate/x-api-endpoint-map)

  * [About the X API](/x-api/getting-started/about-x-api)
</Update>

<Update label="Nov 15, 2021" description="X API v2: Early Access">
  ### Launch of List Lookup Endpoints

  Today, we’re launching the new List lookup endpoints to X API v2. These endpoints will allow users to retrieve details on specified Lists such as followers, members, posts and more. The data retrieved can be used to build solutions that solve for curation, analysis and discoverability use cases and needs. In addition to new List endpoints, a new list: operator has been made available at the Academic Research access level. This will be available to use on search posts and post counts.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/announcing-list-lookup-endpoints-for-the-twitter-api-v2/161965).
</Update>

<Update label="Nov 15, 2021" description="X API v2: Early Access">
  ### Additions to Spaces Endpoints

  We are adding functionality to the Spaces endpoint to return the list of people who purchased a ticket to a Space, as well as support for Topics.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/adding-new-functionality-to-spaces-endpoints/161959).
</Update>

<Update label="Nov 3, 2021" description="X API v2: Early Access">
  ### Launch of Manage Posts Endpoints

  Today, we’re launching new manage posts endpoints to the X API v2. In addition to post and post delete functionality,, we’ve added the ability to post polls, tag people in images, create posts with reply settings, and post to Super Followers.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/announcing-manage-tweets-endpoints-for-the-twitter-api-v2/161501).
</Update>

<Update label="Oct 12, 2021" description="X for Websites">
  ### Changes to Embedded Buttons

  Today, we're making some changes to X's embedded buttons. Buttons are now more rounded to match X.com buttons and we've (very slightly) updated our color palette.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/embedded-buttons-have-a-new-look/160528).
</Update>

<Update label="Sep 29, 2021" description="X API v2: Early Access">
  ### Launch of Lists Endpoint Group

  Today, we’re launching the new Lists endpoint group to X API v2. These endpoints will allow you to build solutions that curate and organize posts based on preferences, interests, groups, or topics.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/announcing-new-twitter-api-v2-manage-list-endpoints/159980).
</Update>

<Update label="Sep 22, 2021" description="X API v2: Early Access">
  ### Launch of Mutes Lookup Endpoint

  Today, we’re launching the new [mutes lookup](https://developer.x.com/en/docs/twitter-api/users/mutes/introduction) endpoint to the X API v2. This endpoint will allow authenticated users to retrieve and get information on the accounts they have muted.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/announcing-new-mutes-lookup-endpoint-for-the-twitter-api-v2/159680).
</Update>

<Update label="Sep 9, 2021" description="OAuth 2.0 beta now available">
  ### Launch of OAuth 2.0 Beta

  Today, we’re launching a beta of OAuth 2.0 and fine-grained scopes on the X API v2. . Developers interested in shaping the future of OAuth 2.0 on the X Developer Platform, can request access to the OAuth 2.0 beta.

  OAuth 2.0 is the industry standard for authentication and will allow for a more modern authorization experience.

  The OAuth 2.0 beta lets you test this new functionality in a v2 Project and associated App and give us feedback before a General Availability release. However, since this implementation of OAuth 2.0 is currently in development, we strongly recommend that you refrain from testing on a public, production environment, or app.

  To learn more about this launch, please visit our forum announcement.
</Update>

<Update label="Aug 25, 2021" description="Batch compliance endpoints now available in X API v2">
  ### Launch of Batch Compliance Endpoints

  Today, we’re launching the new [batch compliance endpoints](https://developer.x.com/en/docs/twitter-api/compliance/batch-compliance/introduction) to the X API v2 to make it easier for developers using the X API to keep their X data in compliance with our [Developer Agreement and Policy](https://developer.x.com/en/developer-terms/policy). These endpoints allow developers and researchers to batch upload large amounts of post or User IDs and understand what action is needed to ensure that their datasets reflect user intent and the current state of the content on X.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/new-batch-compliance-endpoints-available-on-the-twitter-api-v2/158534).
</Update>

<Update label="Aug 18, 2021" description="Spaces endpoints now available in X API v2">
  ### Launch of Spaces Endpoints

  Today, we’re launching the new [Spaces endpoints](https://developer.x.com/en/docs/twitter-api/spaces/overview) and a [new top-level Spaces data dictionary](https://developer.x.com/en/docs/twitter-api/data-dictionary/object-model/space) to the X API v2. The Spaces endpoints enable you to lookup Spaces by Space ID or user ID, or using keywords, hashtags, or usernames of people mentioned in a title. The new data dictionary contains relevant information about a Space such as its title, ticketed status, and participant metrics; all user IDs can be expanded into full objects.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/introducing-new-spaces-endpoints-on-the-twitter-api-v2/158213).
</Update>

<Update label="Aug 16, 2021" description="New data object to help clarify video view limitation for Engagement API">
  ### New Object for Video Views Limitation

  Previously, when you requested video view metrics using the enterprise \[Engagement API]/x-api/enterprise-gnip-2.0/fundamentals/engagement-api) on posts that are older than 1800 days old, we delivered a zero value without much context. Today, we will start delivering a new object in these cases called unsupported\_for\_video\_views\_tweet\_ids, which will include a comma-separated list of post IDs that are older than 1800 days old. You will still receive all other requested metrics for these posts in a separate object.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/new-engagement-api-video-views-object-to-clarify-limitation/158163).
</Update>

<Update label="Aug 11, 2021" description="Media alt text field now available in X API v2">
  ### Addition of Alt Text Field

  Today, we are making the alt\_text field available in the X API v2 media object, in order to enable developers to build more consciously for accessibility.

  To request this field, you must pass the expansions=attachments.media\_keys parameter, as well as the media.fields=alt\_text parameter. If included in your request, this field will return the alt text for any posts that include images with alt text.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/media-alt-text-field-now-available-in-twitter-api-v2/157939).
</Update>

<Update label="Jul 14, 2021" description="reposts now available in X API v2">
  ### Launch of Reposts Endpoints

  Today, we’re launching new [reposts](https://developer.x.com/en/docs/twitter-api/tweets/retweets) endpoints to X API v2.  Developers can now use these endpoints to repost or undo a repost on behalf of an authenticated user, or to look up who reposted a given post.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/announcing-new-twitter-api-v2-retweets-endpoints/156827).
</Update>

<Update label="Jun 30, 2021" description="Manage mutes now available in X API v2">
  ### Launch of Manage Mutes Endpoints

  Today, we’re launching new [manage mutes](https://developer.x.com/en/docs/twitter-api/users/mutes/introduction) endpoints to the X API v2. These endpoints will allow authenticated users to mute or unmute accounts.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/announcing-new-manage-mutes-endpoints-for-the-twitter-api-v2/156261).

  We have now reduced the `max_results` that can deliver with the [full-archive search](/x-api/posts/full-archive-search) endpoint when you are requesting the `context_annotations` field with the `tweet.fields` parameter to 100, meaning that you can only pull up to 100 posts with the field per page.
</Update>

<Update label="Jun 29, 2021" description="Redundant connections and backfill are now available with v2 filtered stream and sampled stream">
  ### Reliability Features for Streaming Endpoints

  Today, we are launching two reliability streaming features for X API v2’s filtered stream and sampled stream called backfill and redundant connections, which are now available on the Academic Research product track.

  The redundant connections feature enables you to connect to a given stream two times, which can help to ensure that you maximize streaming up-time in case one of your streams experiences a disconnection.

  Backfill can be utilized by adding the backfill\_minutes parameter and a whole number between one and five to your streaming request, and allows you to request missed data that might have resulted from a disconnected stream.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/new-reliability-and-recovery-functionality-available-for-twitter-api-v2-streaming-endpoints/156244/2).
</Update>

<Update label="Jun 24, 2021" description="post counts now available in X API v2">
  ### Launch of Post Counts Endpoints

  Today, we’re launching the new [post counts endpoints](/x-api/posts/counts/introduction) to the X API v2. This includes two different endpoints: Recent post counts, which is available to all product tracks, and full-archive post counts, which is currently only available to the Academic Research Product Track. You can use these endpoints to receive the count of posts that matches a specified query.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/introducing-new-tweet-counts-endpoints-to-the-twitter-api-v2/155997).
</Update>

<Update label="Jun 21, 2021" description="Improvements to Teams Functionality">
  ### Improvements to Teams

  Today, we’re launching key improvements to the functionality of teams based on feedback we’ve heard from the community. We have updated the style and design of the team page. We also made changes to the invitation flow to make it easier to invite team members or to learn more about why an invitation might have failed. If you have a team account you can check out the changes by viewing the [teams page](https://developer.x.com/en/portal/teams) of the Developer Console. To learn more about teams check out our \[documentation on the subject]\([https://developer.x.com/en/docs/Developer](https://developer.x.com/en/docs/Developer) Console/overview#team) and related \[FAQ]\([https://developer.x.com/en/docs/Developer](https://developer.x.com/en/docs/Developer) Console/faq#dev-portal-management-faq).

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/announcing-improvements-to-the-functionality-of-teams/155447/2).
</Update>

<Update label="Jun 18, 2021" description="Retiring the standard v1.1 GET /help/configuration endpoint">
  ### Retirement of Configuration Endpoint

  Today, we retired the standard v1.1 GET /help/configuration endpoint.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/retiring-the-1-1-configuration-endpoint/153319).
</Update>

<Update label="May 26, 2021" description="Consolidating the oEmbed endpoint">
  ### Consolidation of oEmbed Endpoint

  Today, we’re sharing that the v1.1 oEmbed endpoint will be retired and removed on November 23, 2021, so that new features can be supported in a consistent manner. After that date, the only official and supported API endpoint for X oEmbeds (embedded posts and timelines) will be via publish.x.com/oembed.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/consolidating-the-oembed-functionality/154690/2).
</Update>

<Update label="May 20, 2021" description="Blocks and Likes lookup available in X API v2">
  ### Launch of Blocks and Likes Lookup Endpoints

  Today, we’re launching the new [blocks](/x-api/users/blocks) and [Likes](/x-api/posts/likes) lookup endpoints to the X API v2. These endpoints enable you to use the v2 API to get information about which posts an account has liked, what users have liked a post, and who you or an authenticated user has blocked.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/announcing-twitter-api-v2-likes-lookup-and-blocks-lookup/154353).
</Update>

<Update label="Apr 22, 2021" description="Manage Likes available in X API v2">
  ### Launch of Manage Likes Endpoints

  Today, we’re launching the new [manage Likes](https://developer.x.com/en/docs/twitter-api/tweets/likes) endpoints to the X API v2. These endpoints enable you to use the v2 API to like and unlike posts.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/announcing-new-manage-likes-endpoints-for-thetwitter-api-v2/152780).
</Update>

<Update label="Apr 7, 2021" description="Manage blocks available in X API v2">
  ### Launch of Manage Blocks Endpoints

  Today, we’re launching the new [manage blocks](/x-api/users/blocks) endpoints to the X API v2. These endpoints enable you to block or unblock accounts on behalf of a user using user IDs.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/announcing-manage-blocks-for-twitter-api-v2/152358/2).
</Update>

<Update label="Mar 3, 2021" description="Removing support for Embedded Like, Collection, and Moment Timelines">
  ### Removal of Support for Embedded Timelines

  Today we’re sharing our plans for the future of [embedded timeline widgets](https://developer.x.com/en/docs/x-for-websites/timelines/overview). On June 23rd 2021, we plan to retire the Likes, Collections, and Moments timelines. We recommended you use the [Profile](https://developer.x.com/en/docs/x-for-websites/timelines/guides/profile-timeline) and [Lists](https://developer.x.com/en/docs/x-for-websites/timelines/guides/list-timeline) timelines, which we’re updating to become faster, easier to use, and more up-to-date with X features and functionality.

  You can learn more about this change in our [forum announcement](https://devcommunity.x.com/t/removing-support-for-embedded-like-collection-and-moment-timelines/150313).
</Update>

<Update label="Feb 10, 2021" description="Manage follows available in X API v2">
  ### Launch of Manage Follows Endpoints

  Today, we’re launching the new [manage follows](/x-api/users/follows) endpoints to the X API v2. These endpoints enable you to follow or unfollow accounts on behalf of a user using their user ID. This launch comes just a few months after the launch of the [follows lookup](/x-api/users/follows) endpoints, which allow you to retrieve an account’s followers and who they are following.

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/introducing-the-new-manage-follows-endpoints-to-the-twitter-api-v2/149465).
</Update>

<Update label="Jan 26, 2021" description="Introducing the X API v2 Academic Research product track">
  ### Introduction of Academic Research Product Track

  Today, we are introducing the new [Academic Research product track](/resources/fundamentals/developer-apps) to [X API v2](/x-api/introduction). This update introduces a new application process for Academic Researchers that will provide those that are approved with an Academic Research [Project](/resources/fundamentals/developer-apps) that will unlock greater access and advanced functionality.

  With the new Academic Research product track, you will be able to access the following:

  * The new X API v2 [full-archive search endpoint](/x-api/posts/full-archive-search), which is only available to the Academic Research product track at this time.

  * An increased [post cap](/x-api/fundamentals/post-cap) of 10 million, up from the 500,000 that is available to the [Standard product track](/resources/fundamentals/developer-apps) at the Basic [access level](https://developer.x.com/en/products/x-api/early-access/guide#na_2).

  * New filter operators available to [recent search](/x-api/posts/recent-search), [full-archive search](/x-api/posts/full-archive-search), and [filtered stream](/x-api/posts/filtered-stream), including `$` (aka cashtag), `bio` (only available via filtered stream), `bio_name` (only available via filtered stream), `bio_location` (only available via filtered stream), `place`, `place_country`, `point_radius`, `bounding_box`, `-is:nullcast`, `has:cashtags` and `has:geo`.

  * An increased rule limit for filtered stream of 1,000 concurrent rules, up from the 25 that is available to the Standard product track at the Basic access level.

  * An increased query and rule character limit of 1,024 characters long, up from the 512 character limit that is available to the Standard product tack at the Basic access level

  To learn more about this launch, please visit our [forum announcement](https://devcommunity.x.com/t/introducing-the-new-academic-research-product-track/148632).
</Update>

<Update label="Dec 18, 2020" description="Conversation reply settings post field for v2 X API">
  ### Addition of Reply Settings Field

  Today we are launching a new field in the post object called reply\_settings. This field is available on all X API v2 endpoints that return posts including post lookup, hide replies, recent search, sampled stream, filtered stream, follows lookup, user post timeline, and user mention timeline endpoints or by [expanding](/x-api/fundamentals/expansions) the post object in any endpoint.

  This field indicates how the post author has allowed others to reply to their posts, whether it’s everyone, just the people they mention in the post, or those they follow. The field values returned by the `reply_settings` field include `everyone`, `mentionedUsers`, and `following`. If no conversation controls are set for the post, this will still show up in the post object with `everyone` value for the field.
</Update>

<Update label="Dec 17, 2020" description="User post timeline and user mention timeline available in X API v2">
  ### Launch of User Post and Mention Timeline Endpoints

  Today, we’re launching the new [user post timeline and user mention timeline endpoints](/x-api/posts/timelines) to the X API v2. These endpoints enable you to request the posts composed by, or mentioning, a specified account on X. Learn more in the forum post announcement.
</Update>

<Update label="Dec 17, 2020" description="Follows lookup available in the X API v2">
  ### Launch of Follows Lookup Endpoints

  Today, we’re launching the new [follows lookup endpoints](/x-api/users/follows) to the X API v2. These endpoints enable you to retrieve an account’s followers and who they are following using their user ID. Learn more in the forum post announcement.
</Update>

<Update label="Nov 16, 2020" description="Retiring some Labs v2 endpoints">
  ### Retirement of Labs v2 Endpoints

  Retired Labs v2 recent search and hide replies endpoints

  We have retired the following endpoints. If you were using the Labs versions of these endpoints, you can use the linked migration guides to update your integration to start using the new X API v2 versions:

  * [Recent search v2](/x-api/posts/search/migrate/overview)

  * [Hide replies v2](/x-api/posts/hide-replies/migrate)

  We also have additional details about migration to the new X API v2 via our [migration hub](/x-api/migrate/overview).

  If you have any questions, please reach out to our [Labs forum category](https://devcommunity.x.com/c/labs/57).
</Update>

<Update label="Oct 12, 2020" description="Retiring some Labs v1 endpoints">
  ### Retirement of Labs v1 Endpoints

  On August 12th, 2020, we launched the new X API v2: Early access. With this release, we graduated several endpoints to X API v2 from the Labs program, and announced that the Labs version of the endpoints would remain in a deprecated state for 60 days before retiring them.

  Today marks 60 days since the launch, meaning that we have retired the following endpoints. If you are using the Labs versions of these endpoints, you can use the linked migration guides to update your integration to start using the new X API v2 versions:

  * post metrics v1

  * Filtered stream v1

  * Sampled stream v1

  We also have additional details about migration to the new X API v2 via our [migration hub](/x-api/migrate/overview).

  If you have any questions, please reach out to our [Labs forum category](https://devcommunity.x.com/c/labs/57).
</Update>

<Update label="Sep 3, 2020" description="post consumption status bar added to the new Developer Console experience">
  ### Addition of Post Consumption Status Bar

  In the [main dashboard page](https://developer.x.com/en/portal/dashboard) of the new Developer Console, you can now check your usage towards the [post cap](/x-api/fundamentals/post-cap) of 500,000 posts per month. This cap is applied at the Project level, across the following v2 endpoints in Basic access: filtered stream, and recent search.

  In order to see this feature and use the new v2 endpoints, you will need to activate the [new Developer Console experience](https://developer.x.com/en/portal/opt-in.html).
</Update>

<Update label="Aug 19, 2020" description="Hide replies available in v2 X API">
  ### Launch of Hide Replies Endpoint

  Today, we’re launching the new hide replies endpoint into the v2 X API. This endpoint enables you to hide abusive, distracting, or misleading replies to posts – a crucial piece to improving the health of the public conversation. Learn more in the forum post announcement.

  The same endpoint in X Developer Labs is now deprecated, and it will be retired in 90 days. Learn how to [migrate to the v2 endpoint.](/x-api/posts/hide-replies#comparing-twitter-apis-hide-replies-endpoints)
</Update>

<Update label="Aug 12, 2020" description="X API v2: Early Access released">
  ### Early Access to X API v2 Endpoints

  Today we announced [Early Access to the first endpoints of the new X API](https://blog.x.com/developer/en_us/topics/tools/2020/introducing_new_twitter_api.html)!

  The new X API features a new API foundation which will allow us to deliver new functionality faster; an updated data format and new functionality that gives you more control over which fields you receive; new post, user, and media fields; and a set of updated endpoints that enable you to listen to and analyze posts, including the following:

  * [post lookup](/x-api/posts/post-lookup-by-post-ids)

  * [User lookup](/x-api/users/user-lookup-by-id)

  * [Recent search](/x-api/posts/recent-search)

  * [Filtered stream](/x-api/posts/filtered-stream)

  * [Sampled stream](/x-api/stream/stream-sampled-posts)

  You can find a full list of the new functionality available, and find migration resources on our \[X API v2: Early Access docs page][https://developer.x.com/en/docs/x-api/early-access](https://developer.x.com/en/docs/x-api/early-access)).

  Learn more about what we have planned in our “\[Guide to the future of the X API][https://developer.x.com/en/docs/x-api/early-access)”](https://developer.x.com/en/docs/x-api/early-access\)”).
</Update>

<Update label="Aug 12, 2020" description="Deprecating certain Labs endpoints">
  ### Deprecation of Labs Endpoints

  We are deprecating certain Labs endpoints due to the launch of their X API v2 replacements in this release.

  The following Labs v1 endpoints will be retired 60 days from today's release:

  * post metrics v1

  * Filtered stream v1

  * Sampled stream v1

  The following Labs v2 endpoint will be retired 90 days from today’s release:

  * Recent search v2
</Update>

<Update label="Jul 13, 2020" description="Improvements to Hide replies">
  ### Improvements to Hide Replies

  We added the ability to unhide a reply. Additionally, previously unhidden replies can now be hidden again via this endpoint.

  Get more details in the [Hide replies documentation](https://developer.x.comhttps://developer.x.com/en/docs/labs).
</Update>

<Update label="Jul 8, 2020" description="Retiring certain Labs v1 endpoints">
  ### Retirement of Labs v1 Endpoints

  Today we are retiring the Labs v1 posts and users, hide replies, and recent search endpoints.

  You can read more about our Labs v1 plan in our [forum announcement](https://devcommunity.x.com/t/update-on-labs-v1-endpoints/138641).
</Update>

<Update label="Jul 7, 2020" description="quotes available for the /totals endpoint">
  ### Addition of Quote Tweets Metric

  Today, the `quote_tweets` metric is now available for 'unowned' posts via the [/totals](/x-api/enterprise-gnip-2.0/fundamentals/engagement-api#post-insights-engagement) endpoint. This means that you can access the quote count for all posts by using app-only authentication.

  You can read more about this change in our [forum post](https://devcommunity.x.com/t/how-the-new-retweets-and-comments-metric-is-returned-with-the-twitter-api/139131).
</Update>

<Update label="Jul 1, 2020" description="Adding two new posts metrics">
  ### Addition of New Post Metrics

  Today we are adding two new non-public metrics subfields, `user_profile_clicks` and `url_link_clicks`, to the post object in the X Developer Labs post lookup endpoints. They will be returned when using the `tweet.fields` parameter with any of the following values: `non_public_metrics`, `organic_metrics`, or `promoted_metrics`.

  To learn more, please visit the [post lookup API reference](https://developer.x.com/en/docs/labs/tweets-and-users/api-reference/get-tweets-id)
</Update>

<Update label="Jun 15, 2020" description="Changes to X web, iOS and Android repost counts">
  ### Changes to Repost Counts

  Starting today, X web, iOS and Android will be showing the total 'reposts and comments' count per post. Using the X API, the total 'reposts and comments' number matching the X interface can be calculated by adding the `retweet_count` and `quote_count` when available. Additionally `quote_count` will be the total unique accounts that have quoted the post, rather than the total posts quoting the post. For more details, please see our [forum post](https://devcommunity.x.com/t/how-the-new-retweets-and-comments-metric-is-returned-with-the-twitter-api/139131/2).
</Update>

<Update label="May 28, 2020" description="Defining organic and promoted metrics groupings for post and media objects">
  ### Organic and Promoted Metrics Groupings

  We are adding `organic_metrics` and `promoted_metrics` to the post and media objects in the post lookup endpoints.
</Update>

<Update label="May 6, 2020" description="Metrics in posts and recent search endpoints">
  ### Addition of Metrics to Endpoints

  We are adding metrics to the post and media objects in the post lookup and recent search endpoints.

  You can read more about these changes in our [forum announcement](https://devcommunity.x.com/t/adding-metrics-to-the-tweets-and-recent-search-endpoints-in-labs/135315)
</Update>

<Update label="Apr 29, 2020" description="COVID-19 Stream and Compliance endpoints">
  ### Launch of COVID-19 Endpoints

  Today we are launching a new COVID-19 stream endpoint and an accompanying compliance endpoint.

  You can read more about these changes in our [forum announcement.](https://devcommunity.x.com/t/new-covid-19-stream-endpoint-available-in-twitter-developer-labs/135540)
</Update>

<Update label="Mar 31, 2020" description="PowerTrack's Replay API now delivers current user profile data">
  ### Updates to Replay API User Profiles

  Starting today, the Replay API will deliver user profile objects that reflect the referenced user at the time the Replay API is running. This change to deliver current user profile objects is similar to the recent Historical PowerTrack update below from Nov. 25, 2019.
</Update>

<Update label="Mar 23, 2020" description="post annotations in posts and recent search endpoints">
  ### Addition of Post Annotations

  We are adding annotations to the post object in the posts and recent search endpoints.

  You can read more about this change in our [forum announcement](https://devcommunity.x.com/t/adding-annotations-to-tweets-and-recent-search-endpoints-in-labs/135193).
</Update>

<Update label="Mar 10, 2020" description="Major updates to the X Developer Policy">
  ### Updates to Developer Policy

  Today, we announced a significant [update to the Developer Policy](https://developer.x.com/en/developer-terms/policy). We encourage you to read more about this via our [forum](https://devcommunity.x.com/t/a-new-easier-to-understand-twitter-developer-policy/135038) and [blog](https://blog.x.com/developer/en_us/topics/community/2020/twitter_developer_policy_update.html) posts, and to review the revised policy. The Developer Policy is one of the foundations for your use of the X API and it is important to understand your commitments.
</Update>

<Update label="Feb 26, 2020" description="Introducting the hide replies endpoint">
  ### Launch of Hide Replies Endpoint

  We want to help people feel safe and comfortable having conversations on X. As part of that, today we’re excited to give post authors more control over the conversations they start by supporting the hide replies feature with a new [endpoint](/x-api/posts/hide-replies).

  You can read more about this new endpoint in our [forum announcement](https://devcommunity.x.com/t/introducing-the-hide-replies-endpoint/134683).
</Update>

<Update label="Feb 25, 2020" description="v2 of Labs endpoints: posts and Users, Recent Search, Hide Replies">
  ### Release of v2 Labs Endpoints

  Today, we are bringing our posts and Users, Recent Search and Hide Replies endpoints to v2 of Labs. We are deprecating Labs v1 endpoints and will fully retire them 90 days after this initial release. We will also keep our v1 documentation available for this duration. You can provide us feedback on this versioning strategy via our [feedback channel](https://twitterdevfeedback.uservoice.com/).

  We're releasing the following changes to posts and Users:

  * Introduce [fields](/x-api/fundamentals/fields) as a query parameter

  * Remove [formats](https://developer.x.com/en/docs/labs#payload) as a query parameter

  * Add path variable for single ID [lookup](https://developer.x.com/en/docs/labs/overview/versioning/migration-guide#id-lookup-path) in posts and Users

  * Adjusting the path and query parameters for single and multi-username [lookup](/x-api/migrate/overview#username-lookup-path) in GET /users

  * Change field name `stats` to `public_metrics`

  Other changes include:

  * Remove the `most_recent_tweet_id` expansion in Users

  * Remove HTML tags from the `source` field in posts to make that field easier to parse

  The core search, pagination and other functionality of Recent Search will stay the same.

  We have put together some [migration materials](/x-api/migrate/overview) for when you update from v1 to v2.

  You can read more about this change in our [forum announcement](https://devcommunity.x.com/t/releasing-a-new-version-of-labs-endpoints/134219).
</Update>

<Update label="Feb 7, 2020" description="X API: Enterprise">
  ### Addition of Drop/Undrop Events to Compliance Firehose

  Today we added new drop/undrop event types to the Compliance Firehose API. You can read more about them in our [documentation.](/x-api/enterprise-gnip-2.0/fundamentals/firehouse)
</Update>

<Update label="Jan 21, 2020" description="X API: Standard v1.1">
  ### Changes to Access Token Management

  Today, we're making changes to the way that Access Tokens and Access Token Secrets are presented and managed within the [applications Dashboard on developer.x.com](https://developer.x.com/content/developer-twitter/en/apps).

  In order to make API integrations more secure, we will no longer show the Access Token and Access Token Secret on the Dashboard beyond the first time that these values are generated.

  After the first time, these credentials can not be retrieved. You will be able to regenerate the tokens on the Dashboard, but this will invalidate your current token and secret.

  You can read more about this change in our [forum announcement](https://devcommunity.x.com/t/upcoming-changes-to-access-token-and-secret-management/130851).
</Update>

<Update label="Jan 15, 2020" description="X API: Standard v1.1">
  ### Removal of SPDY Support

  Starting January 15, 2020, all connections to the X API (and all other X domains) will no longer support SPDY connections.

  You can read more about this change in our [forum announcement](https://devcommunity.x.com/t/removing-support-for-spdy-protocol-on-twitter/132530).
</Update>

<Update label="Jan 6, 2020" description="New Recent search endpoint available in Labs">
  ### Launch of Recent Search Endpoint in Labs

  Today, we are releasing a new endpoint to [search for posts posted in the last 7 days](/x-api/posts/recent-search).

  Learn more about this launch via our [forum announcement.](https://devcommunity.x.com/t/new-recent-search-endpoint-available-in-labs/133076)
</Update>

<Update label="Dec 29, 2019" description="X API: Standard v1.1">
  ### Update to Twurl CLI

  A new updated major release of our X API CLI, `[twurl](https://github.com/twitter/twurl)`, is now available. This release includes a number of bug fixes and enhancements and introduces Bearer Token support which helps to add functionality around the Premium and X Developer Labs endpoints. Read more in our [forum post](https://devcommunity.x.com/t/twurl-0-9-5-released/132966).
</Update>

<Update label="Dec 10, 2019" description="post annotations added to the post Object for sampled stream and filtered stream endpoints in Labs">
  ### Addition of Post Annotations in Streams

  Today in X Developer Labs, we are releasing new metadata elements to the default post payload. These new fields, rendered as part of the post payload, will provide more contextual information about the post.

  Learn more about this launch via our [forum announcement](https://devcommunity.x.com/t/tweet-annotations-added-to-the-tweet-object-for-the-sampled-stream-and-filtered-stream-endpoints-in-labs/132407).
</Update>

<Update label="Nov 25, 2019" description="X API: Enterprise v1.1">
  ### Updates to Historical PowerTrack User Profiles

  Today, we’re updating our "batch historical posts" endpoint (Historical PowerTrack) to provide user profile location, bio description, and display name information that reflects values in place at the of the job processing. When the updated user objects are delivered, there will be a new "updated" string array in the User/Actor object.

  There are up to three possible values: name, description, location:

  `"updated": ["name", "description", "location"]`

  See the [documentation on Historical PowerTrack's data format](https://aem-author-production-version-6-3.twitter.biz/content/developer-twitter/en/docs/tweets/batch-historical/guides/powertrack-data-format.html) for more details.
</Update>

<Update label="Oct 29, 2019" description="X API: Premium v1.1">
  ### Addition to Account Activity API

  Today, we’re releasing a new feature to the Account Activity API that will provide developers with the ability to view whether an account that mentions your subscribed user is blocked.

  You can read more about the `user_has_blocked` [data object structure](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#account-activity-data-object-structure) and check out our [forum announcement](https://devcommunity.x.com/t/new-release-account-activity-api-user-has-blocked-field/131157) for more details.
</Update>

<Update label="Oct 22, 2019" description="New sampled stream endpoint available in Labs">
  ### Launch of Sampled Stream Endpoint in Labs

  Today, we are releasing a new endpoint to [stream a sample of all public posts](/x-api/posts/recent-search) in real-time, as they are posted.

  Learn more about this launch via our [forum announcement.](https://devcommunity.x.com/t/new-sampled-stream-endpoint-available-in-labs/130958)
</Update>

<Update label="Sep 18, 2019" description="New filtered stream endpoint available in Labs">
  ### Launch of Filtered Stream Endpoint in Labs

  Today, we are releasing a [new streaming endpoint](/x-api/posts/filtered-stream) to retrieve posts, and an endpoint to manage your filters in X Developer Labs. With these endpoints, you will be able to retrieve up to 500,000 posts per month (maximum 50 posts per second); you can set up to 10 filter rules on your stream (these can be applied at the same time).

  Learn more about this launch via our [forum announcement](https://devcommunity.x.com/t/new-filtered-stream-endpoints-available-in-labs-and-the-future-of-statuses-filter/129888).

  Requests parameters documented in the API reference pages are now clearly marked as either optional or required. Additionally, API reference pages will describe a JSON body payload when this is allowed by a request.
</Update>

<Update label="Aug 27, 2019" description="New post metrics are now available in Labs">
  ### Launch of Post Metrics in Labs

  You can now retrieve engagement data for any post or list of posts from owned/authorized accounts. The posts you query must be no older than 30 days and cannot be reposts.

  [GET /tweets/metrics/private](https://developer.x.com/en/docs/labs/tweet-metrics/overview.html) supports the following metrics:

  * `impressions`

  * `reposts`

  * `quotes`

  * `likes`

  * `replies`

  * `video views`

  * `video view quartiles` (where the requester is also the author of the media)

  Learn more about this launch via our [forum announcement](https://devcommunity.x.com/t/new-twitter-developer-labs-release-metrics-endpoint/129122).
</Update>

<Update label="Aug 15, 2019" description="X API: Standard v1.1">
  ### Changes to DM Permissions

  Starting today, applications that need to create Direct Messages will be required to have "Read, Write, and Direct Messages" app permissions (RW+DM). Applications attempting to create Direct Messages with only the RW app permission will receive the following error:

  `{"code": 93,"message": "This application is not allowed to access or delete your direct messages."}`

  You can learn more about this change via our [forum announcement](https://devcommunity.x.com/t/updates-to-app-permissions-direct-message-write-permission-change/128221).
</Update>

<Update label="Aug 12, 2019" description="New expansion for GET /users: pinned post in X Developer Labs">
  ### Addition of Pinned Post Expansion

  `pinned_tweet_id` will expand a user’s pinned post through our user object expansion.
</Update>

<Update label="Jul 31, 2019" description="New metadata available for quote counts">
  ### Addition of Quote Counts Metadata

  Developers can use the new Labs endpoints to pull counts of quotes.
</Update>

<Update label="Jul 31, 2019" description="New expansion for GET /users: most recent post">
  ### Addition of Most Recent Post Expansion

  `most_recent_tweet_id` will expand a user’s most recent post through our user object expansion.

  Learn more about this launch via our [forum announcement](https://devcommunity.x.com/t/update-to-twitter-developer-labs/128060).
</Update>

<Update label="Jul 25, 2019" description="X API: Standard v1.1">
  ### Requirement for TLS 1.2

  Today, all connections to the X API (and all other X domains) will require TLS 1.2.

  You can read more about this change in our [forum announcement](https://devcommunity.x.com/t/removing-support-for-legacy-tls-versions-1-0-1-1-on-twitter/126648/2).
</Update>

<Update label="Jul 15, 2019" description="X API: Premium v1.1">
  ### New Account Activity API Endpoint

  Starting today, we are introducing the new [Account Activity API endpoint](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#api-reference) to deactivate user subscriptions using application-only OAuth.

  This new endpoint offers developers the convenience of only having to provide a bearer token to deactivate a subscription, without requiring the subscribed user’s access token.

  We are immediately marking the existing enterprise Account Activity API endpoint used to deactivate user subscriptions with 3-Legged OAuth as deprecated. The endpoint will be retired and no longer be available starting from January 15, 2020.

  Developers can learn more about this API in our [documentation](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#api-reference).
</Update>

<Update label="Jun 20, 2019" description="New expansions for GET /tweets: referenced author and mentioned user">
  ### New Expansions for Tweets Endpoint

  We added two new expansions to the \[GET /tweets][https://developer.x.com/en/docs/labs/tweets-and-users/api-reference/get-tweets.html](https://developer.x.com/en/docs/labs/tweets-and-users/api-reference/get-tweets.html)) endpoint:

  entities.mentions.username will expand the username of any recognized user mention in a post into a full user object.

  `referenced_tweets.id.author_id` expands the ID of the author of any referenced post, when one of the posts requested is a repost, Quoted post or Reply. This expansion will also expand the referenced post ID into a full object.
</Update>

<Update label="Jun 11, 2019" description="GET /tweets and GET /users are now supported in Labs">
  ### Support for Tweets and Users Endpoints in Labs

  The first two endpoints are now available via the Labs portal. Make sure you have an approved developer account and have applied for Labs access to get started with these endpoints.

  [Key differences](https://developer.x.com/content/developer-twitter/en/docs/labs/overview/whats-new) from equivalent v1.1 functionality include:

  * Single endpoint for single object "show" function and batch "lookups"

  * \[Expansion parameters]) support the inclusion of additional objects as part of one request (e.g. mentioned users, referenced posts, e.g.)

  * \[Format parameters]) support different data projections with more or less verbose payloads

  * Rate limiting is at the app level, regardless of auth method (user context or bearer token)

  Learn more about this launch via our [forum announcement](https://devcommunity.x.com/t/twitter-developer-labs-is-open-to-all-developers/126717).
</Update>

<Update label="Jun 10, 2019" description="X API: Standard v1.1">
  ### Retirement of Terms and Privacy Endpoints

  We have fully retired the Terms of Service and Privacy Endpoints. The current status of our [Privacy Policy](https://x.com/en/privacy) and [Terms of Service](https://x.com/en/tos) is best served by our up-to-date web pages.

  You can learn more about this change via our [forum announcement](https://devcommunity.x.com/t/terms-of-service-and-privacy-endpoints-will-no-longer-serve-content-after-june-10/125714).
</Update>

<Update label="May 21, 2019" description="X API: Standard v1.1">
  ### Changes to User Object Fields

  Today some user object fields, including user.lang, will start returning 'null' for updated metadata fields previously announced in our [forum post](https://devcommunity.x.com/t/upcoming-changes-to-user-object-and-get-users-suggestions-endpoints/124732).

  Developers can learn about this change through our [documentation.](/x-api/fundamentals/data-dictionary/reference#user)
</Update>

<Update label="May 20, 2019" description="X API: Enterprise v1.1">
  ### Launch of Account Activity Replay API

  Starting today, we are introducing the [Account Activity Replay API](/x-api/enterprise-gnip-2.0/fundamentals/account-activity), a data recovery tool available with the enterprise tier of the [Account Activity API](/x-api/enterprise-gnip-2.0/fundamentals/account-activity)

  The [Account Activity Replay API](/x-api/enterprise-gnip-2.0/fundamentals/account-activity) allows you to retrieve events from as far back as five days. It should be utilized to recover data in scenarios where your [webhook](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#api-reference) server misses events

  Developers can learn more about this API in our [documentation](/x-api/enterprise-gnip-2.0/fundamentals/account-activity).
</Update>

<Update label="May 6, 2019" description="X API: Standard v1.1">
  ### Support for Native Media in Quotes

  Starting today, native media (photos, videos, and GIFs) can be added to quotes on X, which will be shown as additional media metadata in the entities sections of quote payloads.

  Developers can learn more about this in our [documentation](https://developer.x.com/en/docs/x-api/v1/data-dictionary/object-model/tweet).
</Update>

<Update label="Feb 13, 2019" description="X API: Enterprise v1.1">
  ### Addition of is:reply Operator

  Today, the operator is:reply becomes available to use with the [enterprise search APIs](/x-api/enterprise-gnip-2.0/fundamentals/search-api) and the paid version of the [premium search endpoints](https://developer.x.com/content/developer-twitter/en/docs/tweets/search/api-reference/premium-search).

  The is:reply Boolean operator can be used to filter all replies to posts, or to filter out explicit replies that match a rule. This operator functions in the same way as the is:quote operator.

  Remember that, with the Search API, all ‘is:’ and ‘has:’ operators must be used in conjunction with a standalone operator like a keyword or hashtag.

  You can learn more about this operator in the [documentation](/x-api/enterprise-gnip-2.0/fundamentals/rules-filtering).
</Update>

<Update label="Feb 6, 2019" description="X API: Premium v1.1">
  ### Changes to Expanded URL Enrichment

  Today, the expanded URL enrichment will no longer contain the unwound URL object and metadata (including the title and description fields) for URLs linking to posts, Moments, or profiles. Please note that other URLs (to websites, etc.) will continue to be enriched with this metadata, and the url, expanded\_url, and `display_url` will still be available. This change applies to [Decahose](/x-api/enterprise-gnip-2.0/fundamentals/decahose-api), [PowerTrack](/x-api/enterprise-gnip-2.0/powertrack-api), [Historical PowerTrack](https://developer.x.com/content/developer-twitter/en/docs/tweets/batch-historical/overview), and the [Search APIs](https://developer.x.com/en/docs/x-api/v1/tweets/search/overview).
</Update>

<Update label="Nov 29, 2018" description="X API: Enterprise v1.1">
  ### Addition of is:reply Operator in PowerTrack

  Today, we are introducing a new operator, is:reply, to help you narrow conversations to those you care about most. You can now filter out replies from your results (in addition to the pre-existing ability to filter out reposts, is:retweet, and Quoted posts, is:quote). This new operator is available today within [PowerTrack](/x-api/enterprise-gnip-2.0/powertrack-api), [Historical PowerTrack](https://developer.x.com/content/developer-twitter/en/docs/tweets/batch-historical/overview), and [Replay](/x-api/enterprise-gnip-2.0/powertrack-api#replay-api).

  The is:reply Boolean operator can be used to filter all replies to posts, or to filter out explicit replies that match a rule. This operator functions in the same way as the is:quote operator.

  You can learn more about this operator in the [documentation](/x-api/enterprise-gnip-2.0/fundamentals/rules-filtering).
</Update>

<Update label="Nov 19, 2018" description="X API: Standard v1.1">
  ### Access to Apps in Developer Console

  Today, we've added the ability for developers to view and edit their existing [X apps](/resources/fundamentals/developer-apps) via the [X app dashboard](https://developer.x.com/content/developer-twitter/en/apps) on developer.x.com as long as they're logged into their X account. Previously, you could only view and edit your existing X apps on developer.x.com if you had applied or been approved for a [developer account](/resources/fundamentals/developer-portal).

  You still must have an approved developer account to be able to create new X apps.
</Update>

<Update label="Nov 7, 2018" description="X API: Standard v1.1">
  ### Support for Video Subtitles

  Today, we are announcing that advertisers and publishers are now able to add subtitle files (SRT) to their videos via ads.x.com, Media Studio and our publisher upload API. Subtitles will be viewable on auto-playing video (when no sound is available) on Android and Web. We will release the functionality for iOS in the coming weeks.

  To read more about the new subtitles endpoints, please review their respective API reference pages:

  * [POST media/subtitles-create](/x-api/media/create-media-subtitles)

  * [POST media/subtitles-delete](/x-api/media/delete-media-subtitles)
</Update>

<Update label="Nov 5, 2018" description="X API: Premium v1.1">
  ### Update to Account Activity API Endpoint

  Today we are announcing an update to the [Account Activity API](/x-api/enterprise-gnip-2.0/fundamentals/account-activity) endpoint, [GET subscriptions/count](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#get-direct-messages-events-list#get-account-activity-subscriptions-count). To enable greater visibility into your billing details and use of the API, beginning today, you can programmatically pull the number of provisioned subscriptions associated with your Account Activity API instance within the JSON.  This means you can now see both what your provisioned number of subscriptions are, and how close you are to hitting that limit via the GET subscriptions/count API endpoint.

  This update has been documented with the [Account Activity API documentation](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#get-direct-messages-events-list#get-account-activity-subscriptions-count).
</Update>

<Update label="Oct 22, 2018" description="X API: Standard v1.1">
  ### New Rate Limits on POST Endpoints

  Today we are implementing new app-level rate limits on several of our standard POST endpoints:

  * [POST statuses/update](https://developer.x.com/en/docs/x-api/v1/tweets/post-and-engage/api-reference/post-statuses-update)

  * [POST statuses/retweet/:id](https://developer.x.com/en/docs/x-api/v1/tweets/post-and-engage/api-reference/get-statuses-retweets-id)

  * [POST favorites/create](https://developer.x.com/en/docs/x-api/v1/accounts-and-users/follow-search-get-users/api-reference/post-friendships-create)

  * [POST direct\_messages/events/new](https://developer.x.com/en/docs/x-api/v1/direct-messages/sending-and-receiving/api-reference/new-event)

  * [POST friendships/create](https://developer.x.com/en/docs/x-api/v1/accounts-and-users/follow-search-get-users/api-reference/post-friendships-create)

  You can read more about this change in our [forum announcement](https://devcommunity.x.com/t/new-post-endpoint-rate-limit-enforcement-begins-today/115355).
</Update>

<Update label="Oct 10, 2018" description="X API: Standard v1.1">
  ### Update to twitter-text Library

  Today, we are announcing an update to the [twitter-text](https://github.com/twitter/twitter-text) library to account for the recent changes to the way that X counts emojis. If an emoji previously counted as more than two characters, its count will now be reduced to just two characters to allow for users to make the most out of their 280 characters.

  You can read more about this change in our [forum announcement](https://devcommunity.x.com/t/new-update-to-the-twitter-text-library-emoji-character-count/114607).
</Update>

<Update label="Sep 17, 2018" description="X API: Standard v1.1">
  ### Retirement of Legacy DM Endpoints

  We have fully retired the legacy Direct Message endpoints. You can find a list of the retired DM endpoints, as well as their replacements on \[this page]\([https://developer.x.com/content/developer-twitter/en/docs/direct-messages/sending-and-receiving/api-reference](https://developer.x.com/content/developer-twitter/en/docs/direct-messages/sending-and-receiving/api-reference).

  You can learn more about this update via our [forum announcement](https://devcommunity.x.com/t/details-and-what-to-expect-from-the-api-deprecations-this-week-on-august-16-2018/110746).
</Update>

<Update label="Sep 11, 2018" description="X API: Standard v1.1">
  ### Changes to DM Media Access

  Today, we are implementing some changes to the process where you [retreive attached media from Direct Messages](https://developer.x.com/en/docs/x-api/v1/direct-messages/message-attachments/overview). We will no longer support accessing `media_url` or `media_url_https` via an authenticated [www.x.com](http://www.x.com) session. The request to fetch `media_url_https` MUST always be signed with the user’s access token using OAuth 1.0A.

  You can learn more about this update via our [forum announcement](https://devcommunity.x.com/t/direct-message-api-change-to-how-apps-can-access-images-sent-in-direct-messages/112722).
</Update>

<Update label="Aug 23, 2018" description="X API: Enterprise v1.1">
  ### Retirement of User and Site Streams

  We have fully retired [User Streams](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#migration-introduction) and [Site Streams](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#migration-introduction).

  You can learn more about this update via our [forum announcement](https://devcommunity.x.com/t/details-and-what-to-expect-from-the-api-deprecations-this-week-on-august-16-2018/110746).
</Update>

<Update label="Aug 20, 2018" description="X API: Enterprise v1.1">
  ### New Version of Usage API

  Today we are launching a new version of the Usage API. With this update, we’re making the API more stable by moving to a new system.

  With the system update, users will experience a data "hole" as developers will only be able to pull data back to May 1, 2018. Therefore for the upcoming year, they will be missing out on a few months of historical data (until June 2019).

  A product name is changing within the Usage API from Historical PowerTrack Subscription to Historical PowerTrack 2.0 which will make the product naming consistent with the rest of our user-facing wording. Customers will receive the exact same data in the same format with the update. You will see this change within the products.type JSON object.

  If you have any questions, please reach out to your account manager.
</Update>

<Update label="Aug 16, 2018" description="X API: Standard v1.1">
  ### API Deprecations

  The [Account Activity API DM Beta](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#migration-introduction) product was fully retired today.

  The following services and endpoints will experience degraded service starting today:

  * [User Streams](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#migration-introduction)

  * [Site Streams](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#migration-introduction)

  * [GET direct\_messages](https://developer.x.com/en/docs/x-api/v1/direct-messages/sending-and-receiving/api-reference/list-events)

  * [GET direct\_messages/sent](https://developer.x.com/content/developer-twitter/en/docs/direct-messages/sending-and-receiving/api-reference/get-sent-message)

  * [GET direct\_messages/show](https://developer.x.com/content/developer-twitter/en/docs/direct-messages/sending-and-receiving/api-reference/get-message)

  * [POST direct\_messages/new](https://developer.x.com/content/developer-twitter/en/docs/direct-messages/sending-and-receiving/api-reference/new-message)

  * [POST direct\_messages/destroy](https://developer.x.com/content/developer-twitter/en/docs/direct-messages/sending-and-receiving/api-reference/delete-message)

  User Streams and Site Streams will be fully retired on August 23rd.

  The legacy Direct Messages endpoints will be fully retired on September 17th.

  You can learn more about this update via our [forum announcement](https://devcommunity.x.com/t/details-and-what-to-expect-from-the-api-deprecations-this-week-on-august-16-2018/110746).
</Update>

<Update label="Jul 24, 2018" description="X API: Standard v1.1">
  ### Changes to App Creation and Rate Limits

  As of today, you will no longer be able to create new [X apps](/resources/fundamentals/developer-apps) via [apps.x.com](https://apps.x.com/). You will now be redirected to either your [Developer Console](/resources/fundamentals/developer-portal) account or, if you don't have a Developer Console account yet, to the page where [you can apply](https://developer.x.com/content/developer-twitter/en/apply-for-access).

  We also announced that we will be implementing new app-level rate limits to the following POST endpoints on September 10th, 2018.

  * [POST statuses/update](https://developer.x.com/en/docs/x-api/v1/tweets/post-and-engage/api-reference/post-statuses-update)

  * [POST statuses/retweet:id](https://developer.x.com/en/docs/x-api/v1/tweets/post-and-engage/api-reference/post-statuses-retweet-id)

  * [POST friendships/create](https://developer.x.com/en/docs/x-api/v1/accounts-and-users/follow-search-get-users/api-reference/post-friendships-create)

  * [POST favorites/create](https://developer.x.com/en/docs/x-api/v1/tweets/post-and-engage/api-reference/post-favorites-create)

  * [POST direct\_messages/events/new](https://developer.x.com/en/docs/x-api/v1/direct-messages/sending-and-receiving/api-reference/new-event)

  Finally, we are introducing a new option for people to report suspected violations of our platform policies to you for review.

  You can learn more about all of these updates via our [blog post](https://cli.re/g32qKr).
</Update>

<Update label="Jun 21, 2018" description="X API: Standard v1.1">
  ### App Management in Developer Console

  If you have a [Developer Console](/resources/fundamentals/developer-portal) account, you can now create and manage your [X apps](/resources/fundamentals/developer-apps). Please read our \[forum post]\([https://devcommunity.x.com/t/app-creation-and-management-now-available-in-the-Developer](https://devcommunity.x.com/t/app-creation-and-management-now-available-in-the-Developer) Console/107723) for more details.
</Update>

<Update label="Jun 12, 2018" description="X API: Standard v1.1">
  ### Changes to Sign in with X and Account Activity

  Today, we started requiring that you register the [callback URLs](/resources/fundamentals/developer-apps#callback-urls) that you use with the Sign in with X process. You can read more about this update [here](https://devcommunity.x.com/t/action-required-sign-in-with-twitter-users-must-whitelist-callback-urls/105342).

  We also announced the addition of the tweet\_delete\_events activity to the Account Activity API. This new activity will be sent for those corresponding deleted events to enable developers to more easily provide a compliant experience for their customers and application users. You can read more about this new activity in our [forum post](https://devcommunity.x.com/t/adding-delete-events-to-the-account-activity-api/106783) or on our [documentation](/x-api/enterprise-gnip-2.0/fundamentals/account-activity).
</Update>

<Update label="May 25, 2018" description="X API: Standard v1.1">
  ### Updates to Terms and Policies

  Today, we made some changes to our [Terms of Service](https://x.com/en/tos), [Privacy Policy](https://x.com/en/privacy), and \[X Developer Agreement][https://developer.x.com/en/developer-terms/agreement-and-policy](https://developer.x.com/en/developer-terms/agreement-and-policy) that include privacy, security, and data protection updates. Please read our [forum post](https://devcommunity.x.com/t/upcoming-changes-to-the-developer-platform/104603) for more details.
</Update>

<Update label="May 23, 2018" description="X API: Standard v1.1">
  ### Timezone Fields Made Private

  Today, the timezone values in X user objects became private fields. From here on out, all\* time\_zone and utc\_offset data objects will return as null. Please read our [forum post](https://devcommunity.x.com/t/upcoming-changes-to-the-developer-platform/104603) for more details.
  \* They will continue to be available on the account/settings endpoint, for authenticated users only.
</Update>

<Update label="May 21, 2018" description="X API: Enterprise v1.1">
  ### Removal of Klout Data

  Today, we removed all Klout data from post payloads as part of our GDPR updates.
</Update>

<Update label="May 14, 2018" description="X API: Standard v1.1">
  ### Changes to Profile Background and Account Activity

  Today, we are changing all instances of profile\_background\_image\_url and profile\_background\_image\_url\_https to their default values. Please read our [forum post](https://devcommunity.x.com/t/upcoming-changes-to-the-developer-platform/104603) for more details.

  In addition to the above change, we are adding a new field to the [Account Activity API](/x-api/enterprise-gnip-2.0/fundamentals/account-activity) payloads to reference which subscription the activity was delivered for. This JSON object is called for\_user\_id and will include the subscribed user's ID who produced that activity as its value. You can see some examples of this new JSON object in our [account activity objects](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#account-activity-data-object-structure) page.
</Update>

<Update label="May 10, 2018" description="X API: Standard v1.1">
  ### Changes to Quote Payload Rendering

  Today, we are adding a change to the way that URLs will be rendered in the quote payload.

  We’re adding a new entity called the "quoted\_status\_permalink" entity to ensure the quoted post can be referenced and we will be removing the t.co link from the quoted post "text" field.

  With the new format, the t.co link is no longer appended to the "text" field of the quoted post in the "quoted\_status" object.

  Further, we will no longer put the quoted post t.co url, expanded\_url, and display\_url in the ‘urls’ entity. Instead, these will be added to a new "quoted\_status\_permalink" object with "url", "expanded", and "display" URL attributes. This means that the "quoted\_status\_permalink" object will be reserved for the t.co link back to the quoted post, whereas the "entities.urls" array can be used to identify any links shared within the original post or quote.

  Please read our [forum post](https://devcommunity.x.com/t/updating-how-urls-are-rendered-in-the-quote-tweet-payload/105473) and [updated documentation](https://devcommunity.x.com/t/upcoming-changes-to-the-developer-platform/104603) for more details.
</Update>

<Update label="Apr 30, 2018" description="X for Websites">
  ### Deprecation of X Kit

  The announcement of [X Kit](https://developer.x.com/en/docs/x-for-websites) deprecation, after October 31, 2018 X Kit will no longer be actively maintained.  Please read our [blog post](https://blog.x.com/developer/en_us/topics/tools/2018/discontinuing-support-for-twitter-kit-sdk.html) for more details.
</Update>

<Update label="Apr 24, 2018" description="X API: Standard v1.1">
  ### Platform Updates for GDPR

  Today we announced several updates to the platform related to GDPR. Please read our [forum post](https://devcommunity.x.com/t/upcoming-changes-to-the-developer-platform/104603) for more details.
</Update>

<Update label="Mar 1, 2018" description="X API: Enterprise v1.1">
  ### Addition of Additional Media Info Object

  The addition of a new object to the post payload – additional\_media\_info object – and also restricting some video details (video\_info) for promoted posts where advertisers have requested we limit video playback to X owned clients. You can find additional information about this change at the following link: [Extended Entities Objects > post with native video](https://developer.x.com/en/docs/x-api/v1/data-dictionary/object-model/extended-entities).
</Update>

<Update label="Feb 1, 2018" description="X API: Premium v1.1">
  ### Launch of Premium Full-Archive Search

  Launch of the [premium full-archive search endpoint](https://blog.x.com/developer/en_us/topics/tools/2018/access-the-full-history-of-tweets.html).
</Update>

<Update label="Dec 19, 2017" description="X API: Premium v1.1">
  ### Launch of Account Activity APIs

  Launched both ([All Activities](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#migration-introduction)) and ([Direct Messages](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#migration-introduction)) Standard beta Account Activity APIs, read more about this launch [on our blog](https://blog.x.com/developer/en_us/topics/tools/2017/announcing-more-functionality-to-improve-customer-engagements-on-twitter.html).  Announced User streams & Site streams deprecation and sunset date of Tuesday June 19, 2018.
</Update>

<Update label="Dec 15, 2017" description="X API: Standard v1.1">
  ### Update to twitter-text Library

  Version 2.0 of twitter-text is now available [on GitHub](https://github.com/twitter/twitter-text). This update addresses the change in our character limit that was rolled out on November 7th, 2017. To learn more about this update, please [visit our forum](https://devcommunity.x.com/t/shipped-twitter-text-2-0/98577).
</Update>

<Update label="Nov 14, 2017" description="X API: Premium v1.1">
  ### Launch of Premium APIs

  Launched the Premium APIs.

  These new APIs build on the quality and stability of our enterprise data platform, and make it available more widely via a tiered pricing model. For the first time, you can start to search across 30 days of posts (instead of the limited 7 days of data on the standard endpoint), and optionally, you can also access our premium enrichments for profile geo, URL expansion, and poll data. Here’s a taste of some of the new features:

  * More posts per request (Sandbox + Premium)

  * A far more rich query language enabling more complex queries (Sandbox + Premium)

  * A counts endpoint that returns time-series counts of posts (Premium)

  * Metadata enrichments, such as expanded URLs and Profile Geo (Premium)

  Read more about this launch [on our blog](https://blog.x.com/developer/en_us/topics/tools/2017/introducing-twitter-premium-apis.html).
</Update>

<Update label="Nov 7, 2017" description="X API: Standard v1.1">
  ### Launch of 280 Character Posts

  Official launch of 280 character posts in languages where cramming was an issue. Please see our [forum announcement](https://devcommunity.x.com/t/updating-the-character-limit-and-the-twitter-text-library/96425) or official [blog post](https://blog.x.com/official/en_us/topics/product/2017/tweetingmadeeasier.html) for further reference.
</Update>

<Update label="Nov 1, 2017" description="X API: Standard v1.1">
  ### Removal of DM Commands in Statuses/Update

  The ability to send Direct Messages via the statuses/update API endpoint has been completely removed, and the `enable_dm_commands` and `fail_dm_commands` parameters will no longer have any effect. Read more about this update [on our forum](https://devcommunity.x.com/t/retiring-legacy-dm-commands-on-the-standard-tweet-api/86653 "on our forum").
</Update>

<Update label="Oct 11, 2017" description="X API: Standard v1.1">
  ### Changes to OAuth Login Flow

  A change was made to X’s backend OAuth API endpoints which altered the behaviour of the /oauth/authenticate endpoint to match that of the /oauth/authorize endpoint. Read more about this update [on our forum](https://devcommunity.x.com/t/recent-changes-to-twitter-s-oauth-login-flow-and-api-endpoints/94943).
</Update>

<Update label="Oct 10, 2017" description="X API: Enterprise v1.1">
  ### Updates to Engagement API Metrics

  The Engagement API was updated to use the same metrics aggregation methodology in use by the X analytics dashboard. Read more about this update [on our forum](https://devcommunity.x.com/t/changes-to-the-engagement-api/94523).
</Update>

<Update label="Oct 1, 2017" description="X API: Standard v1.1">
  ### Changes to DM Commands Failure

  The default value of the `fail_dm_commands` parameter within the DM statuses/update endpoint has been switched to *true*. All status updates intended as Direct Messages will start to return errors (unless `enable_dm_commands` is *false*, in which case the post will be posted). Read more about this update [on our forum](https://devcommunity.x.com/t/retiring-legacy-dm-commands-on-the-standard-tweet-api/86653).
</Update>

<Update label="Sep 26, 2017" description="X API: Standard v1.1">
  ### Treatment of 280 Character Tweets

  The response payload for 280 character tweets will be treated the same way as long tweets. Read more about this update [on our forum](https://devcommunity.x.com/t/testing-280-characters-for-certain-languages/94126).
</Update>

<Update label="Sep 11, 2017" description="X API: Standard v1.1">
  ### Addition of Additional Media Info

  Adding new data to the post payload (`additional_media_info object`) and also restricting some video details (`video_info`) for promoted posts where advertisers have requested we limit video playback to X owned clients. You can find additional information about this change at the following link: [Extended Entities Objects > post with native video](https://developer.x.com/en/docs/x-api/v1/data-dictionary/object-model/extended-entities)
</Update>

<Update label="Aug 7, 2017" description="X API: Enterprise v1.1">
  ### End of Support for url\_contains Operator in 30-Day Search

  30-Day and Full-Archive Search ended support for url\_contains: operator. Deprecation of this operator was announced as part of the Gnip 2.0 migration in August 2016. Any Search query using the url\_contains: Operator will be rejected as invalid.
</Update>

<Update label="Jul 6, 2017" description="X API: Enterprise v1.1">
  ### Upcoming Removal of url\_contains Operator in Search APIs

  The 30-Day Search API (both 30-Day and Full-Archive) will no longer support the url\_contains: operator beginning 30 days from today, or after August 4, 2017 (Support of url\_contains: will actually end with the first deploy after that date). Deprecation of this operator was announced as part of the Gnip 2.0 migration in August 2016. When Operator support is ended, any query using the url\_contains: will be rejected as invalid.
</Update>

<Update label="Jun 2, 2017" description="X API: Standard v1.1">
  ### Retirement of xAuth

  The xAuth authentication mechanism has been removed from all X APIs  Read more about this update [on our forum](https://devcommunity.x.com/t/retirement-of-xauth/88022).
</Update>

<Update label="May 8, 2017" description="X API: Standard v1.1">
  ### HTTP Headers Forced to Lowercase

  All HTTP headers have been forced into lowercase (`content-type`, `x-rate-limit-remaining`, `x-access-level` etc). Read more about this update [on our forum](https://devcommunity.x.com/t/upcoming-http-header-changes/86715).
</Update>

<Update label="May 5, 2017" description="X API: Standard v1.1">
  ### Optional Parameters for DM Commands

  The optional `enable_dm_commands` parameter to statuses/update will enable applications to remove DM command support early, before the transition period ends. The default value is *true* (i.e. current legacy behavior), but this may be set to *false* to get the new, post-November 1 behavior. The optional fail\_dm\_commands parameter to statuses/update will make DM commands return HTTP 403 (error code 151) from the API when set to *true*. The default value is *false*. Read more about this update [on our forum](https://devcommunity.x.com/t/retiring-legacy-dm-commands-on-the-standard-tweet-api/86653).
</Update>

<Update label="Apr 25, 2017" description="X API: Enterprise v1.1">
  ### Support for Emojis in Rules

  Rules with emojis are now available in the enterprise Search APIs
</Update>

<Update label="Apr 6, 2017" description="X API: Standard v1.1">
  ### Wider Availability of Direct Message APIs

  Access to several new Direct Message APIs are now more widely available. Read more about this update [on our blog](https://blog.twitter.com/developer/en_us/topics/tools/2017/new-apis-to-power-the-future-of-customer-engagement-in-direct-me.html).
</Update>

<Update label="Mar 9, 2017" description="X API: Standard v1.1">
  ### Retirement of MPEG-DASH Video Support

  MPEG-DASH URLs (.mpd) has been removed from the payload of a post that contains video. Read more about this update [on our forum](https://devcommunity.x.com/t/retiring-mpeg-dash-video-support-on-march-9th-2017/82761).
</Update>

<Update label="Feb 22, 2017" description="X API: Enterprise v1.1">
  ### New Enrichments and Payload Changes

  New Enrichment! Poll Metadata is now available through our enterprise APIs. See the [documentation](/x-api/enterprise-gnip-2.0/fundamentals/account-activity#migration-introduction) for more details.

  New payload field: Image Alt-Text (decription) field may be present in the entities.media\[] and extended\_entities.media\[] section of the payload if a user chooses chooses the "Add description" option when adding a photo to a post. This is available in enriched native format only.

  Default payload format: Newly created streams on Gnip products will now default to orriginal format JSON.
</Update>

<Update label="Jan 23, 2017" description="X API: Enterprise v1.1">
  ### Updates to Historical PowerTrack and Replay API

  Historical PowerTrack API & Replay API

  * quote filtering is now supported

  * Quoted posts are now fully rehydrated within HPT and Replay post payloads
</Update>

<Update label="Jan 17, 2017" description="X API: Enterprise v1.1">
  ### New Payload Fields for Counts

  New payload fields: quote\_count and reply\_count are now available in native enriched format payloads across Realtime and Historical APIs
</Update>

<Update label="Dec 20, 2016" description="X API: Enterprise v1.1">
  ### Support for Geo Operators in Full-Archive Search

  Full-Archive Search API (FAS):

  * Added support for additional geo operators:

  * place:

  * place\_country:

  * has:profile\_geo:

  * profile\_country:

  * profile\_region:

  * profile\_locality:
</Update>

<Update label="Dec 5, 2016" description="X API: Enterprise v1.1">
  ### Rule Management by ID in PowerTrack

  Rule management (GET and DELETE) by Rule ID is now available for PowerTrack 2.0 and PowerTrack Replay 2.0
</Update>

<Update label="Nov 10, 2016" description="X API: Enterprise v1.1">
  ### Support for Geo Operators in 30-Day Search

  30-Day Search API:

  * Added support for additional geo operators:

  * place:

  * place\_country:

  * has:profile\_geo:

  * profile\_country:

  * profile\_region:

  * profile\_locality:
</Update>