X — Snapshot Change
ChangedPrevious snapshot
15 Oct 2026, 18:00 (Berlin)
660452d945aa7af3157a939b0a3d605b…
This snapshot
17 Oct 2026, 18:00 (Berlin)
9f54c264d95316bc74065e51ea730a16…
Run Assessment
significant ollama / llama3.1:8bA new set of links to dataset documentation and transparency pages were added, including a link to the Ad Transparency center. This makes the change significant because it provides researchers with access to new information about the platform's data collection and usage practices.
+ 12 lines added
− 39 lines removed
14 links added
https://help.x.com/en/rules-and-policies/dsa-vetted-researchers
Links Changed
Added
Line-by-line changes
65 lines
| [Skip to main content](https://help.x.com/en/rules-and-policies/dsa-vetted-researchers#main-content) | |
| [Sign In](https://x.com/login?redirect_after_login=https%3A%2F%2Fhelp.x.com%2Fen) | |
| ⋯ 58 unchanged lines ⋯ | |
| | Category | Description | Data Structure & Metadata | Suggested Access Modalities | | |
| | --- | --- | --- | --- | | |
| − | | Content and Interaction Data | Public post identification, creation time, edit history, referenced posts, indication of content recognized as sensitive, public engagement metrics, such as like count, comments, reposts, views, and information on who can interact with a post.More information on content and interaction data that may be requested can be found here. | >x< API: The Post object has a long list of ‘root-level’ fields, such as id, text, and created\_at. Post objects are also the ‘parent’ object to several child objects including user, media, poll, and place. Use the field parameter Post.fields when requesting these root-level fields on the Post object. Examples of Post object metadata can be found here. | >x< API (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | | User Related Data | Public profile information, such as >x< handle, date of creation, bio description, if ID verified, specified location, account label and checkmarks (e.g., parody label, affiliation badges, blue checkmarks, etc.), user activity details (e.g., follower count, following count, post count, etc.). More information on user related data that may be requested can be found here. | >x< API: The user object contains >x< user account metadata describing the referenced user. The user object is the primary object returned in the users lookup endpoint. When requesting additional user fields on this endpoint, use the fields parameter user.fieldshere. | >x< API (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | | Community Notes Data | Community Note id, creation time, post id for which the Community Note was requested or applied, user-entered source link, initial status rating, rescore timestamp, rating, hashed user identifiers, etc.More information on Community Notes data that may be requested can be found here. | Download Community Notes Data: All Community Notes contributions are publicly available here. The Community Notes data is released as separate files. Note-related tables can be joined on the noteId field to create a combined dataset with hashed user identifiers and information about notes and their ratings. More information can be found here. >x< API: The Community Notes endpoints allows AI note writers to search for and propose Community Notes on >x< programmatically. Use of the API requires your account being signed up for >x< Developer AI access and enrolled in Community Notes as an AI Note Writer. | Download Community Notes data (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | | Content Recommendations | Open source code on algorithmic recommendations, which serves content across all product surfaces (e.g., For You, Explore, Notifications, Search, etc.). Repository allows researchers to review the actual infrastructure driving content recommendation for all users without compromising user safety and privacy (which requires protecting model weights and training data). This provides researchers the opportunity to understand how user engagement data feeds into the recommendation system and the machinations of that system to then source and recommend a certain pool of content. More information on >x<’s content recommendation system can be found here and here. | Github Repositories: >x<’s Github Repositories include the main repo and ml repo containing the source code for many parts of >x<, including our recommendations algorithm.Data may be in formats such as Scala (majority), Java, Python, Rust, JavaScript/TypeScript, Markdown (.md), ASCII diagrams, PlantUML, etc. The READMEs of each project contain instructions about how to run each project. | >x< API (suitable for all types of data expressly identified herein)Github Repositories (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | | Ads Served in the EU | For ads served in the EU, the Ad Transparency center includes the following: Advertiser, Funding Entity, the Advertiser’s Main Parameters for serving the advertisement (e.g. particular groups, etc), Impression, and Reach of Ad to provide transparency around advertisements on the platform. The >x< Ads Repository also provides information related to ads halted from running on the platform.More information can be found here. | >x< Ads Transparency Center: To access the Ads Repository to search for a particular account, country, and date range, use the user interface or the >x< API (instructions here). The request will generate a .csv file containing the information about the applicable advertisement(s). | >x< Ads Transparency Center (suitable for all types of data expressly identified herein)>x< API (generally suitable for all types of low-risk data)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | | Content Moderation | Number of content reports, actions taken on content reports, own initiative content moderation actions, grounds for action, number of complaints and appeals statistics.More information on >x<’s content moderation practices and the types of data that may be requested can be found in >x<’s DSA Transparency Reports available here. | Dependent on the type of data (.csv file, etc.). | The access modality for this type of data is dependent on the types of data requests, but may include >x< DSA Transparency Report as well as secure processing environments. | |
| − | |
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | |
| − | | --- | --- | --- | --- | |
| − | | Content and Interaction Data | Public post identification, creation time, edit history, referenced posts, indication of content recognized as sensitive, public engagement metrics, such as like count, comments, reposts, views, and information on who can interact with a post.More information on content and interaction data that may be requested can be found here. | >x< API: The Post object has a long list of ‘root-level’ fields, such as id, text, and created\_at. Post objects are also the ‘parent’ object to several child objects including user, media, poll, and place. Use the field parameter Post.fields when requesting these root-level fields on the Post object. Examples of Post object metadata can be found here. | >x< API (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | | User Related Data | Public profile information, such as >x< handle, date of creation, bio description, if ID verified, specified location, account label and checkmarks (e.g., parody label, affiliation badges, blue checkmarks, etc.), user activity details (e.g., follower count, following count, post count, etc.). More information on user related data that may be requested can be found here. | >x< API: The user object contains >x< user account metadata describing the referenced user. The user object is the primary object returned in the users lookup endpoint. When requesting additional user fields on this endpoint, use the fields parameter user.fieldshere. | >x< API (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | | Community Notes Data | Community Note id, creation time, post id for which the Community Note was requested or applied, user-entered source link, initial status rating, rescore timestamp, rating, hashed user identifiers, etc.More information on Community Notes data that may be requested can be found here. | Download Community Notes Data: All Community Notes contributions are publicly available here. The Community Notes data is released as separate files. Note-related tables can be joined on the noteId field to create a combined dataset with hashed user identifiers and information about notes and their ratings. More information can be found here. >x< API: The Community Notes endpoints allows AI note writers to search for and propose Community Notes on >x< programmatically. Use of the API requires your account being signed up for >x< Developer AI access and enrolled in Community Notes as an AI Note Writer. | Download Community Notes data (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | | Content Recommendations | Open source code on algorithmic recommendations, which serves content across all product surfaces (e.g., For You, Explore, Notifications, Search, etc.). Repository allows researchers to review the actual infrastructure driving content recommendation for all users without compromising user safety and privacy (which requires protecting model weights and training data). This provides researchers the opportunity to understand how user engagement data feeds into the recommendation system and the machinations of that system to then source and recommend a certain pool of content. More information on >x<’s content recommendation system can be found here and here. | Github Repositories: >x<’s Github Repositories include the main repo and ml repo containing the source code for many parts of >x<, including our recommendations algorithm.Data may be in formats such as Scala (majority), Java, Python, Rust, JavaScript/TypeScript, Markdown (.md), ASCII diagrams, PlantUML, etc. The READMEs of each project contain instructions about how to run each project. | >x< API (suitable for all types of data expressly identified herein)Github Repositories (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | | Ads Served in the EU | For ads served in the EU, the Ad Transparency center includes the following: Advertiser, Funding Entity, the Advertiser’s Main Parameters for serving the advertisement (e.g. particular groups, etc), Impression, and Reach of Ad to provide transparency around advertisements on the platform. The >x< Ads Repository also provides information related to ads halted from running on the platform.More information can be found here. | >x< Ads Transparency Center: To access the Ads Repository to search for a particular account, country, and date range, use the user interface or the >x< API (instructions here). The request will generate a .csv file containing the information about the applicable advertisement(s). | >x< Ads Transparency Center (suitable for all types of data expressly identified herein)>x< API (generally suitable for all types of low-risk data)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | | Content Moderation | Number of content reports, actions taken on content reports, own initiative content moderation actions, grounds for action, number of complaints and appeals statistics.More information on >x<’s content moderation practices and the types of data that may be requested can be found in >x<’s DSA Transparency Reports available here. | Dependent on the type of data (.csv file, etc.). | The access modality for this type of data is dependent on the types of data requests, but may include >x< DSA Transparency Report as well as secure processing environments. | |
| − | |
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | |
| − | | --- | --- | --- | --- | |
| − | | Content and Interaction Data | Public post identification, creation time, edit history, referenced posts, indication of content recognized as sensitive, public engagement metrics, such as like count, comments, reposts, views, and information on who can interact with a post.More information on content and interaction data that may be requested can be found here. | >x< API: The Post object has a long list of ‘root-level’ fields, such as id, text, and created\_at. Post objects are also the ‘parent’ object to several child objects including user, media, poll, and place. Use the field parameter Post.fields when requesting these root-level fields on the Post object. Examples of Post object metadata can be found here. | >x< API (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | |
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | |
| − | | --- | --- | --- | --- | |
| − | | User Related Data | Public profile information, such as >x< handle, date of creation, bio description, if ID verified, specified location, account label and checkmarks (e.g., parody label, affiliation badges, blue checkmarks, etc.), user activity details (e.g., follower count, following count, post count, etc.). More information on user related data that may be requested can be found here. | >x< API: The user object contains >x< user account metadata describing the referenced user. The user object is the primary object returned in the users lookup endpoint. When requesting additional user fields on this endpoint, use the fields parameter user.fieldshere. | >x< API (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | |
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | |
| − | | --- | --- | --- | --- | |
| − | | Community Notes Data | Community Note id, creation time, post id for which the Community Note was requested or applied, user-entered source link, initial status rating, rescore timestamp, rating, hashed user identifiers, etc.More information on Community Notes data that may be requested can be found here. | Download Community Notes Data: All Community Notes contributions are publicly available here. The Community Notes data is released as separate files. Note-related tables can be joined on the noteId field to create a combined dataset with hashed user identifiers and information about notes and their ratings. More information can be found here. >x< API: The Community Notes endpoints allows AI note writers to search for and propose Community Notes on >x< programmatically. Use of the API requires your account being signed up for >x< Developer AI access and enrolled in Community Notes as an AI Note Writer. | Download Community Notes data (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | |
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | |
| − | | --- | --- | --- | --- | |
| − | | Content Recommendations | Open source code on algorithmic recommendations, which serves content across all product surfaces (e.g., For You, Explore, Notifications, Search, etc.). Repository allows researchers to review the actual infrastructure driving content recommendation for all users without compromising user safety and privacy (which requires protecting model weights and training data). This provides researchers the opportunity to understand how user engagement data feeds into the recommendation system and the machinations of that system to then source and recommend a certain pool of content. More information on >x<’s content recommendation system can be found here and here. | Github Repositories: >x<’s Github Repositories include the main repo and ml repo containing the source code for many parts of >x<, including our recommendations algorithm.Data may be in formats such as Scala (majority), Java, Python, Rust, JavaScript/TypeScript, Markdown (.md), ASCII diagrams, PlantUML, etc. The READMEs of each project contain instructions about how to run each project. | >x< API (suitable for all types of data expressly identified herein)Github Repositories (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | |
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | |
| − | | --- | --- | --- | --- | |
| − | | Ads Served in the EU | For ads served in the EU, the Ad Transparency center includes the following: Advertiser, Funding Entity, the Advertiser’s Main Parameters for serving the advertisement (e.g. particular groups, etc), Impression, and Reach of Ad to provide transparency around advertisements on the platform. The >x< Ads Repository also provides information related to ads halted from running on the platform.More information can be found here. | >x< Ads Transparency Center: To access the Ads Repository to search for a particular account, country, and date range, use the user interface or the >x< API (instructions here). The request will generate a .csv file containing the information about the applicable advertisement(s). | >x< Ads Transparency Center (suitable for all types of data expressly identified herein)>x< API (generally suitable for all types of low-risk data)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| − | |
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | |
| − | | --- | --- | --- | --- | |
| − | | Content Moderation | Number of content reports, actions taken on content reports, own initiative content moderation actions, grounds for action, number of complaints and appeals statistics.More information on >x<’s content moderation practices and the types of data that may be requested can be found in >x<’s DSA Transparency Reports available here. | Dependent on the type of data (.csv file, etc.). | The access modality for this type of data is dependent on the types of data requests, but may include >x< DSA Transparency Report as well as secure processing environments. | |
| + | | Content and Interaction Data | Public post identification, creation time, edit history, referenced posts, indication of content recognized as sensitive, public engagement metrics, such as like count, comments, reposts, views, and information on who can interact with a post. More information on content and interaction data that may be requested can be found [here](https://docs.x.com/x-api/fundamentals/data-dictionary). | >x< API: The Post object has a long list of ‘root-level’ fields, such as id, text, and created\_at. Post objects are also the ‘parent’ object to several child objects including user, media, poll, and place. Use the field parameter Post.fields when requesting these root-level fields on the Post object. Examples of Post object metadata can be found [here](https://docs.x.com/x-api/fundamentals/data-dictionary#tweet). | [>x< API](https://docs.x.com/x-api/introduction) (suitable for all types of data expressly identified herein) >x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| + | | User Related Data | Public profile information, such as >x< handle, date of creation, bio description, if ID verified, specified location, account label and checkmarks (e.g., parody label, affiliation badges, blue checkmarks, etc.), user activity details (e.g., follower count, following count, post count, etc.). More information on user related data that may be requested can be found [here](https://docs.x.com/x-api/fundamentals/data-dictionary#user). | >x< API: The user object contains >x< user account metadata describing the referenced user. The user object is the primary object returned in the users lookup endpoint. When requesting additional user fields on this endpoint, use the fields parameter user.fields [here](https://docs.x.com/x-api/fundamentals/data-dictionary#user). | [>x< API](https://docs.x.com/x-api/introduction) (suitable for all types of data expressly identified herein) >x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| + | | Community Notes Data | Community Note id, creation time, post id for which the Community Note was requested or applied, user-entered source link, initial status rating, rescore timestamp, rating, hashed user identifiers, etc. More information on Community Notes data that may be requested can be found [here](https://communitynotes.x.com/guide/under-the-hood/download-data). | Download Community Notes Data: All Community Notes contributions are publicly available [here](https://x.com/i/communitynotes/download-data). The Community Notes data is released as separate files. Note-related tables can be joined on the noteId field to create a combined dataset with hashed user identifiers and information about notes and their ratings. More information can be found [here](https://communitynotes.x.com/guide/under-the-hood/download-data). >x< API: The [Community Notes endpoints](https://docs.x.com/x-api/community-notes/introduction) allows AI note writers to search for and propose Community Notes on >x< programmatically. Use of the API requires your account being signed up for >x< Developer AI access and enrolled in Community Notes as an AI Note Writer. | [Download Community Notes data](https://x.com/i/communitynotes/download-data) (suitable for all types of data expressly identified herein) >x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| + | | Content Recommendations | Open source code on algorithmic recommendations, which serves content across all product surfaces (e.g., For You, Explore, Notifications, Search, etc.). Repository allows researchers to review the actual infrastructure driving content recommendation for all users without compromising user safety and privacy (which requires protecting model weights and training data). This provides researchers the opportunity to understand how user engagement data feeds into the recommendation system and the machinations of that system to then source and recommend a certain pool of content. More information on >x<’s content recommendation system can be found [here](https://help.x.com/resources/recommender-systems) and [here](https://github.com/twitter/the-algorithm?tab=readme-ov-file#xs-recommendation-algorithm). | Github Repositories: [>x<’s Github Repositories](https://github.com/twitter/) include the [main repo](https://github.com/twitter/the-algorithm/) and [ml repo](https://github.com/twitter/the-algorithm-ml) containing the source code for many parts of >x<, including our recommendations algorithm. Data may be in formats such as Scala (majority), Java, Python, Rust, JavaScript/TypeScript, Markdown (.md), ASCII diagrams, PlantUML, etc. The READMEs of each project contain instructions about how to run each project. | [>x< API](https://docs.x.com/x-api/introduction) (suitable for all types of data expressly identified herein) [Github Repositories](https://github.com/twitter) (suitable for all types of data expressly identified herein) >x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| + | | Ads Served in the EU | For ads served in the EU, the Ad Transparency center includes the following: Advertiser, Funding Entity, the Advertiser’s Main Parameters for serving the advertisement (e.g. particular groups, etc), Impression, and Reach of Ad to provide transparency around advertisements on the platform. The >x< Ads Repository also provides information related to ads halted from running on the platform. More information can be found [here](https://business.x.com/help/ads-policies/product-policies/ads-transparency). | >x< Ads Transparency Center: To access the Ads Repository to search for a particular account, country, and date range, use the [user interface](https://ads.x.com/ads-repository) or the >x< API ([instructions here](https://business.x.com/help/ads-policies/product-policies/ads-transparency#:~:text=Steps%20for%20API%20Access%20to%20X%20Ads%20Repository%3A)). The request will generate a .csv file containing the information about the applicable advertisement(s). | [>x< Ads Transparency Center](https://business.x.com/help/ads-policies/product-policies/ads-transparency) (suitable for all types of data expressly identified herein) [>x< API](https://docs.x.com/x-api/introduction) (generally suitable for all types of low-risk data) >x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | |
| + | | Content Moderation | Number of content reports, actions taken on content reports, own initiative content moderation actions, grounds for action, number of complaints and appeals statistics. More information on >x<’s content moderation practices and the types of data that may be requested can be found in >x<’s DSA Transparency Reports available [here](https://transparency.x.com/reports/dsa-transparency-report). | Dependent on the type of data (.csv file, etc.). | The access modality for this type of data is dependent on the types of data requests, but may include [>x< DSA Transparency Report](https://transparency.x.com/reports/dsa-transparency-report) as well as secure processing environments. | |
| ### Notes on Catalogue: | |
| ⋯ 69 unchanged lines ⋯ | |
| - [>x< for business](https://business.x.com) | |
| - [Resources and guides](https://business.x.com/resources) | |
| - [1-888-GET-XADS](tel:+18884389237) | |
| + | |
| + | ## Legal |
| + | |
| + | - [Cookies](https://help.x.com/rules-and-policies/twitter-cookies) |
| + | - [Privacy](https://x.com/privacy) |
| + | - [Terms and conditions](https://x.com/tos) |
| Previous · 15 Oct 2026, 18:00 (Berlin) | Current · 17 Oct 2026, 18:00 (Berlin) | |||
|---|---|---|---|---|
| [Skip to main content](https://help.x.com/en/rules-and-policies/dsa-vetted-researchers#main-content) | [Skip to main content](https://help.x.com/en/rules-and-policies/dsa-vetted-researchers#main-content) | |||
| [Sign In](https://x.com/login?redirect_after_login=https%3A%2F%2Fhelp.x.com%2Fen) | [Sign In](https://x.com/login?redirect_after_login=https%3A%2F%2Fhelp.x.com%2Fen) | |||
| ⋯ 58 unchanged lines ⋯ | ||||
| | Category | Description | Data Structure & Metadata | Suggested Access Modalities | | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | | |||
| | --- | --- | --- | --- | | | --- | --- | --- | --- | | |||
| − | | Content and Interaction Data | Public post identification, creation time, edit history, referenced posts, indication of content recognized as sensitive, public engagement metrics, such as like count, comments, reposts, views, and information on who can interact with a post.More information on content and interaction data that may be requested can be found here. | >x< API: The Post object has a long list of ‘root-level’ fields, such as id, text, and created\_at. Post objects are also the ‘parent’ object to several child objects including user, media, poll, and place. Use the field parameter Post.fields when requesting these root-level fields on the Post object. Examples of Post object metadata can be found here. | >x< API (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | + | | Content and Interaction Data | Public post identification, creation time, edit history, referenced posts, indication of content recognized as sensitive, public engagement metrics, such as like count, comments, reposts, views, and information on who can interact with a post. More information on content and interaction data that may be requested can be found [here](https://docs.x.com/x-api/fundamentals/data-dictionary). | >x< API: The Post object has a long list of ‘root-level’ fields, such as id, text, and created\_at. Post objects are also the ‘parent’ object to several child objects including user, media, poll, and place. Use the field parameter Post.fields when requesting these root-level fields on the Post object. Examples of Post object metadata can be found [here](https://docs.x.com/x-api/fundamentals/data-dictionary#tweet). | [>x< API](https://docs.x.com/x-api/introduction) (suitable for all types of data expressly identified herein) >x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |
| − | | User Related Data | Public profile information, such as >x< handle, date of creation, bio description, if ID verified, specified location, account label and checkmarks (e.g., parody label, affiliation badges, blue checkmarks, etc.), user activity details (e.g., follower count, following count, post count, etc.). More information on user related data that may be requested can be found here. | >x< API: The user object contains >x< user account metadata describing the referenced user. The user object is the primary object returned in the users lookup endpoint. When requesting additional user fields on this endpoint, use the fields parameter user.fieldshere. | >x< API (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | + | | User Related Data | Public profile information, such as >x< handle, date of creation, bio description, if ID verified, specified location, account label and checkmarks (e.g., parody label, affiliation badges, blue checkmarks, etc.), user activity details (e.g., follower count, following count, post count, etc.). More information on user related data that may be requested can be found [here](https://docs.x.com/x-api/fundamentals/data-dictionary#user). | >x< API: The user object contains >x< user account metadata describing the referenced user. The user object is the primary object returned in the users lookup endpoint. When requesting additional user fields on this endpoint, use the fields parameter user.fields [here](https://docs.x.com/x-api/fundamentals/data-dictionary#user). | [>x< API](https://docs.x.com/x-api/introduction) (suitable for all types of data expressly identified herein) >x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |
| − | | Community Notes Data | Community Note id, creation time, post id for which the Community Note was requested or applied, user-entered source link, initial status rating, rescore timestamp, rating, hashed user identifiers, etc.More information on Community Notes data that may be requested can be found here. | Download Community Notes Data: All Community Notes contributions are publicly available here. The Community Notes data is released as separate files. Note-related tables can be joined on the noteId field to create a combined dataset with hashed user identifiers and information about notes and their ratings. More information can be found here. >x< API: The Community Notes endpoints allows AI note writers to search for and propose Community Notes on >x< programmatically. Use of the API requires your account being signed up for >x< Developer AI access and enrolled in Community Notes as an AI Note Writer. | Download Community Notes data (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | + | | Community Notes Data | Community Note id, creation time, post id for which the Community Note was requested or applied, user-entered source link, initial status rating, rescore timestamp, rating, hashed user identifiers, etc. More information on Community Notes data that may be requested can be found [here](https://communitynotes.x.com/guide/under-the-hood/download-data). | Download Community Notes Data: All Community Notes contributions are publicly available [here](https://x.com/i/communitynotes/download-data). The Community Notes data is released as separate files. Note-related tables can be joined on the noteId field to create a combined dataset with hashed user identifiers and information about notes and their ratings. More information can be found [here](https://communitynotes.x.com/guide/under-the-hood/download-data). >x< API: The [Community Notes endpoints](https://docs.x.com/x-api/community-notes/introduction) allows AI note writers to search for and propose Community Notes on >x< programmatically. Use of the API requires your account being signed up for >x< Developer AI access and enrolled in Community Notes as an AI Note Writer. | [Download Community Notes data](https://x.com/i/communitynotes/download-data) (suitable for all types of data expressly identified herein) >x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |
| − | | Content Recommendations | Open source code on algorithmic recommendations, which serves content across all product surfaces (e.g., For You, Explore, Notifications, Search, etc.). Repository allows researchers to review the actual infrastructure driving content recommendation for all users without compromising user safety and privacy (which requires protecting model weights and training data). This provides researchers the opportunity to understand how user engagement data feeds into the recommendation system and the machinations of that system to then source and recommend a certain pool of content. More information on >x<’s content recommendation system can be found here and here. | Github Repositories: >x<’s Github Repositories include the main repo and ml repo containing the source code for many parts of >x<, including our recommendations algorithm.Data may be in formats such as Scala (majority), Java, Python, Rust, JavaScript/TypeScript, Markdown (.md), ASCII diagrams, PlantUML, etc. The READMEs of each project contain instructions about how to run each project. | >x< API (suitable for all types of data expressly identified herein)Github Repositories (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | + | | Content Recommendations | Open source code on algorithmic recommendations, which serves content across all product surfaces (e.g., For You, Explore, Notifications, Search, etc.). Repository allows researchers to review the actual infrastructure driving content recommendation for all users without compromising user safety and privacy (which requires protecting model weights and training data). This provides researchers the opportunity to understand how user engagement data feeds into the recommendation system and the machinations of that system to then source and recommend a certain pool of content. More information on >x<’s content recommendation system can be found [here](https://help.x.com/resources/recommender-systems) and [here](https://github.com/twitter/the-algorithm?tab=readme-ov-file#xs-recommendation-algorithm). | Github Repositories: [>x<’s Github Repositories](https://github.com/twitter/) include the [main repo](https://github.com/twitter/the-algorithm/) and [ml repo](https://github.com/twitter/the-algorithm-ml) containing the source code for many parts of >x<, including our recommendations algorithm. Data may be in formats such as Scala (majority), Java, Python, Rust, JavaScript/TypeScript, Markdown (.md), ASCII diagrams, PlantUML, etc. The READMEs of each project contain instructions about how to run each project. | [>x< API](https://docs.x.com/x-api/introduction) (suitable for all types of data expressly identified herein) [Github Repositories](https://github.com/twitter) (suitable for all types of data expressly identified herein) >x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |
| − | | Ads Served in the EU | For ads served in the EU, the Ad Transparency center includes the following: Advertiser, Funding Entity, the Advertiser’s Main Parameters for serving the advertisement (e.g. particular groups, etc), Impression, and Reach of Ad to provide transparency around advertisements on the platform. The >x< Ads Repository also provides information related to ads halted from running on the platform.More information can be found here. | >x< Ads Transparency Center: To access the Ads Repository to search for a particular account, country, and date range, use the user interface or the >x< API (instructions here). The request will generate a .csv file containing the information about the applicable advertisement(s). | >x< Ads Transparency Center (suitable for all types of data expressly identified herein)>x< API (generally suitable for all types of low-risk data)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | + | | Ads Served in the EU | For ads served in the EU, the Ad Transparency center includes the following: Advertiser, Funding Entity, the Advertiser’s Main Parameters for serving the advertisement (e.g. particular groups, etc), Impression, and Reach of Ad to provide transparency around advertisements on the platform. The >x< Ads Repository also provides information related to ads halted from running on the platform. More information can be found [here](https://business.x.com/help/ads-policies/product-policies/ads-transparency). | >x< Ads Transparency Center: To access the Ads Repository to search for a particular account, country, and date range, use the [user interface](https://ads.x.com/ads-repository) or the >x< API ([instructions here](https://business.x.com/help/ads-policies/product-policies/ads-transparency#:~:text=Steps%20for%20API%20Access%20to%20X%20Ads%20Repository%3A)). The request will generate a .csv file containing the information about the applicable advertisement(s). | [>x< Ads Transparency Center](https://business.x.com/help/ads-policies/product-policies/ads-transparency) (suitable for all types of data expressly identified herein) [>x< API](https://docs.x.com/x-api/introduction) (generally suitable for all types of low-risk data) >x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |
| − | | Content Moderation | Number of content reports, actions taken on content reports, own initiative content moderation actions, grounds for action, number of complaints and appeals statistics.More information on >x<’s content moderation practices and the types of data that may be requested can be found in >x<’s DSA Transparency Reports available here. | Dependent on the type of data (.csv file, etc.). | The access modality for this type of data is dependent on the types of data requests, but may include >x< DSA Transparency Report as well as secure processing environments. | | + | | Content Moderation | Number of content reports, actions taken on content reports, own initiative content moderation actions, grounds for action, number of complaints and appeals statistics. More information on >x<’s content moderation practices and the types of data that may be requested can be found in >x<’s DSA Transparency Reports available [here](https://transparency.x.com/reports/dsa-transparency-report). | Dependent on the type of data (.csv file, etc.). | The access modality for this type of data is dependent on the types of data requests, but may include [>x< DSA Transparency Report](https://transparency.x.com/reports/dsa-transparency-report) as well as secure processing environments. | | |
| − | ||||
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | | |||
| − | | --- | --- | --- | --- | | |||
| − | | Content and Interaction Data | Public post identification, creation time, edit history, referenced posts, indication of content recognized as sensitive, public engagement metrics, such as like count, comments, reposts, views, and information on who can interact with a post.More information on content and interaction data that may be requested can be found here. | >x< API: The Post object has a long list of ‘root-level’ fields, such as id, text, and created\_at. Post objects are also the ‘parent’ object to several child objects including user, media, poll, and place. Use the field parameter Post.fields when requesting these root-level fields on the Post object. Examples of Post object metadata can be found here. | >x< API (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |||
| − | | User Related Data | Public profile information, such as >x< handle, date of creation, bio description, if ID verified, specified location, account label and checkmarks (e.g., parody label, affiliation badges, blue checkmarks, etc.), user activity details (e.g., follower count, following count, post count, etc.). More information on user related data that may be requested can be found here. | >x< API: The user object contains >x< user account metadata describing the referenced user. The user object is the primary object returned in the users lookup endpoint. When requesting additional user fields on this endpoint, use the fields parameter user.fieldshere. | >x< API (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |||
| − | | Community Notes Data | Community Note id, creation time, post id for which the Community Note was requested or applied, user-entered source link, initial status rating, rescore timestamp, rating, hashed user identifiers, etc.More information on Community Notes data that may be requested can be found here. | Download Community Notes Data: All Community Notes contributions are publicly available here. The Community Notes data is released as separate files. Note-related tables can be joined on the noteId field to create a combined dataset with hashed user identifiers and information about notes and their ratings. More information can be found here. >x< API: The Community Notes endpoints allows AI note writers to search for and propose Community Notes on >x< programmatically. Use of the API requires your account being signed up for >x< Developer AI access and enrolled in Community Notes as an AI Note Writer. | Download Community Notes data (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |||
| − | | Content Recommendations | Open source code on algorithmic recommendations, which serves content across all product surfaces (e.g., For You, Explore, Notifications, Search, etc.). Repository allows researchers to review the actual infrastructure driving content recommendation for all users without compromising user safety and privacy (which requires protecting model weights and training data). This provides researchers the opportunity to understand how user engagement data feeds into the recommendation system and the machinations of that system to then source and recommend a certain pool of content. More information on >x<’s content recommendation system can be found here and here. | Github Repositories: >x<’s Github Repositories include the main repo and ml repo containing the source code for many parts of >x<, including our recommendations algorithm.Data may be in formats such as Scala (majority), Java, Python, Rust, JavaScript/TypeScript, Markdown (.md), ASCII diagrams, PlantUML, etc. The READMEs of each project contain instructions about how to run each project. | >x< API (suitable for all types of data expressly identified herein)Github Repositories (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |||
| − | | Ads Served in the EU | For ads served in the EU, the Ad Transparency center includes the following: Advertiser, Funding Entity, the Advertiser’s Main Parameters for serving the advertisement (e.g. particular groups, etc), Impression, and Reach of Ad to provide transparency around advertisements on the platform. The >x< Ads Repository also provides information related to ads halted from running on the platform.More information can be found here. | >x< Ads Transparency Center: To access the Ads Repository to search for a particular account, country, and date range, use the user interface or the >x< API (instructions here). The request will generate a .csv file containing the information about the applicable advertisement(s). | >x< Ads Transparency Center (suitable for all types of data expressly identified herein)>x< API (generally suitable for all types of low-risk data)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |||
| − | | Content Moderation | Number of content reports, actions taken on content reports, own initiative content moderation actions, grounds for action, number of complaints and appeals statistics.More information on >x<’s content moderation practices and the types of data that may be requested can be found in >x<’s DSA Transparency Reports available here. | Dependent on the type of data (.csv file, etc.). | The access modality for this type of data is dependent on the types of data requests, but may include >x< DSA Transparency Report as well as secure processing environments. | | |||
| − | ||||
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | | |||
| − | | --- | --- | --- | --- | | |||
| − | | Content and Interaction Data | Public post identification, creation time, edit history, referenced posts, indication of content recognized as sensitive, public engagement metrics, such as like count, comments, reposts, views, and information on who can interact with a post.More information on content and interaction data that may be requested can be found here. | >x< API: The Post object has a long list of ‘root-level’ fields, such as id, text, and created\_at. Post objects are also the ‘parent’ object to several child objects including user, media, poll, and place. Use the field parameter Post.fields when requesting these root-level fields on the Post object. Examples of Post object metadata can be found here. | >x< API (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |||
| − | ||||
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | | |||
| − | | --- | --- | --- | --- | | |||
| − | | User Related Data | Public profile information, such as >x< handle, date of creation, bio description, if ID verified, specified location, account label and checkmarks (e.g., parody label, affiliation badges, blue checkmarks, etc.), user activity details (e.g., follower count, following count, post count, etc.). More information on user related data that may be requested can be found here. | >x< API: The user object contains >x< user account metadata describing the referenced user. The user object is the primary object returned in the users lookup endpoint. When requesting additional user fields on this endpoint, use the fields parameter user.fieldshere. | >x< API (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |||
| − | ||||
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | | |||
| − | | --- | --- | --- | --- | | |||
| − | | Community Notes Data | Community Note id, creation time, post id for which the Community Note was requested or applied, user-entered source link, initial status rating, rescore timestamp, rating, hashed user identifiers, etc.More information on Community Notes data that may be requested can be found here. | Download Community Notes Data: All Community Notes contributions are publicly available here. The Community Notes data is released as separate files. Note-related tables can be joined on the noteId field to create a combined dataset with hashed user identifiers and information about notes and their ratings. More information can be found here. >x< API: The Community Notes endpoints allows AI note writers to search for and propose Community Notes on >x< programmatically. Use of the API requires your account being signed up for >x< Developer AI access and enrolled in Community Notes as an AI Note Writer. | Download Community Notes data (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |||
| − | ||||
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | | |||
| − | | --- | --- | --- | --- | | |||
| − | | Content Recommendations | Open source code on algorithmic recommendations, which serves content across all product surfaces (e.g., For You, Explore, Notifications, Search, etc.). Repository allows researchers to review the actual infrastructure driving content recommendation for all users without compromising user safety and privacy (which requires protecting model weights and training data). This provides researchers the opportunity to understand how user engagement data feeds into the recommendation system and the machinations of that system to then source and recommend a certain pool of content. More information on >x<’s content recommendation system can be found here and here. | Github Repositories: >x<’s Github Repositories include the main repo and ml repo containing the source code for many parts of >x<, including our recommendations algorithm.Data may be in formats such as Scala (majority), Java, Python, Rust, JavaScript/TypeScript, Markdown (.md), ASCII diagrams, PlantUML, etc. The READMEs of each project contain instructions about how to run each project. | >x< API (suitable for all types of data expressly identified herein)Github Repositories (suitable for all types of data expressly identified herein)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |||
| − | ||||
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | | |||
| − | | --- | --- | --- | --- | | |||
| − | | Ads Served in the EU | For ads served in the EU, the Ad Transparency center includes the following: Advertiser, Funding Entity, the Advertiser’s Main Parameters for serving the advertisement (e.g. particular groups, etc), Impression, and Reach of Ad to provide transparency around advertisements on the platform. The >x< Ads Repository also provides information related to ads halted from running on the platform.More information can be found here. | >x< Ads Transparency Center: To access the Ads Repository to search for a particular account, country, and date range, use the user interface or the >x< API (instructions here). The request will generate a .csv file containing the information about the applicable advertisement(s). | >x< Ads Transparency Center (suitable for all types of data expressly identified herein)>x< API (generally suitable for all types of low-risk data)>x< may suggest other modalities, including other secure processing environments for data, based on the type of data and the nature of the risk. | | |||
| − | ||||
| − | | Category | Description | Data Structure & Metadata | Suggested Access Modalities | | |||
| − | | --- | --- | --- | --- | | |||
| − | | Content Moderation | Number of content reports, actions taken on content reports, own initiative content moderation actions, grounds for action, number of complaints and appeals statistics.More information on >x<’s content moderation practices and the types of data that may be requested can be found in >x<’s DSA Transparency Reports available here. | Dependent on the type of data (.csv file, etc.). | The access modality for this type of data is dependent on the types of data requests, but may include >x< DSA Transparency Report as well as secure processing environments. | | |||
| ### Notes on Catalogue: | ### Notes on Catalogue: | |||
| ⋯ 69 unchanged lines ⋯ | ||||
| - [>x< for business](https://business.x.com) | - [>x< for business](https://business.x.com) | |||
| - [Resources and guides](https://business.x.com/resources) | - [Resources and guides](https://business.x.com/resources) | |||
| - [1-888-GET-XADS](tel:+18884389237) | - [1-888-GET-XADS](tel:+18884389237) | |||
| + | ||||
| + | ## Legal | |||
| + | ||||
| + | - [Cookies](https://help.x.com/rules-and-policies/twitter-cookies) | |||
| + | - [Privacy](https://x.com/privacy) | |||
| + | - [Terms and conditions](https://x.com/tos) | |||