21 Telegram

Telegram’s UGC data transparency is assessed through the Telegram API across Brazil, the EU, and the UK, while the platform provides no advertising transparency repository in any of the assessed regions. Under the UGC framework, the API enables free, structured extraction of public content data, supporting author-based search, keyword search, temporal filtering, historical data retrieval without time limits, and near-real-time access. Its most significant limitation is the absence of membership-free, platform-wide content discovery: access is restricted to channels and groups in which the requesting account or bot is already a member. No graphical interface for data extraction is available, and documentation quality is uneven, lacking deprecation policies, per-endpoint rate-limit specifications, and practical usage examples. As a result, Telegram is placed in the Limited band for UGC transparency, reflecting functional but structurally constrained API access. The absence of any advertising transparency infrastructure significantly limits the possibility of independent research into sponsored content on the platform.

21.1 Transparency Assessment

User-Generated Content

Limited

Advertising

Not Available

21.2 User-Generated Content

Coverage: BR, EU, UK

21.2.1 Special Criteria

21.2.1.1 UGC_SC1: Does the platform provide an API that enables the structured extraction of public user-generated content data for independent analysis?

Region	Answer	Note
BR	✅ Yes	Telegram provides an API that enables access to public data from conversations on the platform.
EU	✅ Yes	Telegram provides an API that enables access to public data from conversations on the platform.
UK	✅ Yes	Telegram provides an API that enables access to public data from conversations on the platform.

21.2.1.2 UGC_SC2: Can the full scope of public content data be extracted through the platform’s API?

Region	Answer	Note
BR	❌ No	On Telegram, public user-generated content cannot be globally discovered or retrieved through the API without prior participation or explicit identifiers. Access is limited to channels or groups in which the bot or account is already a member, and there is no endpoint that exposes a comprehensive list of all public channels and groups. The API also returns specific errors when requests are made for supergroups or channels of which the requester is not a member (e.g., `channels.getFullChannel`). As a result, the API does not provide membership-free, platform-wide access to the full corpus of public content.
EU	❌ No	On Telegram, public user-generated content cannot be globally discovered or retrieved through the API without prior participation or explicit identifiers. Access is limited to channels or groups in which the bot or account is already a member, and there is no endpoint that exposes a comprehensive list of all public channels and groups. The API also returns specific errors when requests are made for supergroups or channels of which the requester is not a member (e.g., `channels.getFullChannel`). As a result, the API does not provide membership-free, platform-wide access to the full corpus of public content.
UK	❌ No	On Telegram, public user-generated content cannot be globally discovered or retrieved through the API without prior participation or explicit identifiers. Access is limited to channels or groups in which the bot or account is already a member, and there is no endpoint that exposes a comprehensive list of all public channels and groups. The API also returns specific errors when requests are made for supergroups or channels of which the requester is not a member (e.g., `channels.getFullChannel`). As a result, the API does not provide membership-free, platform-wide access to the full corpus of public content.

21.2.1.3 UGC_SC3: Is access to the platform’s API free of charge?

Region	Answer	Note
BR	✅ Yes	All Telegram APIs are free of charge.
EU	✅ Yes	All Telegram APIs are free of charge.
UK	✅ Yes	All Telegram APIs are free of charge.

21.2.1.4 UGC_SC4: Does the platform offer a graphical interface for extracting data?

Region	Answer	Note
BR	❌ No	The platform does not provide a graphical interface for accessing or extracting public user-generated content data.
EU	❌ No	The platform does not provide a graphical interface for accessing or extracting public user-generated content data.
UK	❌ No	The platform does not provide a graphical interface for accessing or extracting public user-generated content data.

21.2.2 Accessibility

21.2.2.1 UGC_OC1: Can the requested data be extracted directly from the platform’s API response?

Region	Answer	Note
BR	✅ Yes	Responses to requests to the platform API provide the expected data in an appropriate format, without requiring redirection.
EU	✅ Yes	Responses to requests to the platform API provide the expected data in an appropriate format, without requiring redirection.
UK	✅ Yes	Responses to requests to the platform API provide the expected data in an appropriate format, without requiring redirection.

21.2.2.2 UGC_OC2: Does the platform’s API support renewable authentication mechanisms without risk of data loss?

Region	Answer	Note
BR	✅ Yes	The Telegram API access requires an access key that remains the same even after logging in multiple times. It will only change in specific situations, and the API provides the necessary methods to update it programmatically.
EU	✅ Yes	The Telegram API access requires an access key that remains the same even after logging in multiple times. It will only change in specific situations, and the API provides the necessary methods to update it programmatically.
UK	✅ Yes	The Telegram API access requires an access key that remains the same even after logging in multiple times. It will only change in specific situations, and the API provides the necessary methods to update it programmatically.

21.2.2.3 UGC_OC3: Does the platform’s API offer an endpoint for extracting data from an individual publication?

Region	Answer	Note
BR	✅ Yes	It is possible to extract data for a specific message using its unique identifier, as long as the group or public channel it belongs to is known.
EU	✅ Yes	It is possible to extract data for a specific message using its unique identifier, as long as the group or public channel it belongs to is known.
UK	✅ Yes	It is possible to extract data for a specific message using its unique identifier, as long as the group or public channel it belongs to is known.

21.2.2.4 UGC_OC4: Does the platform’s API offer an endpoint for extracting data from an individual author?

Region	Answer	Note
BR	✅ Yes	Telegram offers the `messages.search` endpoint for searching for messages by author, as long as the group or public channel the message belongs to is known.
EU	✅ Yes	Telegram offers the `messages.search` endpoint for searching for messages by author, as long as the group or public channel the message belongs to is known.
UK	✅ Yes	Telegram offers the `messages.search` endpoint for searching for messages by author, as long as the group or public channel the message belongs to is known.

21.2.2.5 UGC_OC5: Does the platform’s API provide an endpoint for extracting data based on search terms?

Region	Answer	Note
BR	✅ Yes	Telegram provides a `messages.searchGlobal` endpoint that allows searching for messages containing specific terms. However, in practice this is limited to public groups and channels that the researcher already knows or in which their account or bot participates. Telegram reportedly offers an expanded global search in a paid tier, but this could not be tested, as the evaluation was conducted using only the free access level across all platforms.
EU	✅ Yes	Telegram provides a `messages.searchGlobal` endpoint that allows searching for messages containing specific terms. However, in practice this is limited to public groups and channels that the researcher already knows or in which their account or bot participates. Telegram reportedly offers an expanded global search in a paid tier, but this could not be tested, as the evaluation was conducted using only the free access level across all platforms.
UK	✅ Yes	Telegram provides a `messages.searchGlobal` endpoint that allows searching for messages containing specific terms. However, in practice this is limited to public groups and channels that the researcher already knows or in which their account or bot participates. Telegram reportedly offers an expanded global search in a paid tier, but this could not be tested, as the evaluation was conducted using only the free access level across all platforms.

21.2.2.6 UGC_OC6: Does the API use locale-neutral data representations?

Region	Answer	Note
BR	✅ Yes	The publication dates returned by the Telegram API follow the ISO 8601 format.
EU	✅ Yes	The publication dates returned by the Telegram API follow the ISO 8601 format.
UK	✅ Yes	The publication dates returned by the Telegram API follow the ISO 8601 format.

21.2.3 Compliance

21.2.3.1 UGC_OC7: Does the platform implement a proper deprecation strategy to avoid breaking client applications while rolling out major changes in the API?

Region	Answer	Note
BR	❌ No	We found no official documentation for the Telegram Database Library (TDLib) that outlines a deprecation policy. While there is a changelog on GitHub, it documents only changes that have already been made to major releases. The document does not include removal dates and migration instructions for deprecated features.
EU	❌ No	We found no official documentation for the Telegram Database Library (TDLib) that outlines a deprecation policy. While there is a changelog on GitHub, it documents only changes that have already been made to major releases. The document does not include removal dates and migration instructions for deprecated features.
UK	❌ No	We found no official documentation for the Telegram Database Library (TDLib) that outlines a deprecation policy. While there is a changelog on GitHub, it documents only changes that have already been made to major releases. The document does not include removal dates and migration instructions for deprecated features.

21.2.3.2 UGC_OC8: Is the platform’s API documentation published in open access?

Region	Answer	Note
BR	✅ Yes	Any user can access the Telegram API documentation.
EU	✅ Yes	Any user can access the Telegram API documentation.
UK	✅ Yes	Any user can access the Telegram API documentation.

21.2.3.3 UGC_OC9: Is the platform’s API documentation clearly written and exemplified?

Region	Answer	Note
BR	❌ No	The Telegram and TDLib API documentation is not clearly written or well exemplified. Although it provides a technical reference of available classes and methods, it lacks detailed explanations and practical examples showing how to call endpoints or implement common workflows. The structure assumes prior familiarity with Telegram’s internal architecture, which makes it difficult for developers to understand how to use the APIs without relying on third-party resources or community libraries. Methods such as `messages.getHistory` and TDLib’s `getMessage` illustrate this lack of clarity, as they do not present expected outputs or practical usage scenarios.
EU	❌ No	The Telegram and TDLib API documentation is not clearly written or well exemplified. Although it provides a technical reference of available classes and methods, it lacks detailed explanations and practical examples showing how to call endpoints or implement common workflows. The structure assumes prior familiarity with Telegram’s internal architecture, which makes it difficult for developers to understand how to use the APIs without relying on third-party resources or community libraries. Methods such as `messages.getHistory` and TDLib’s `getMessage` illustrate this lack of clarity, as they do not present expected outputs or practical usage scenarios.
UK	❌ No	The Telegram and TDLib API documentation is not clearly written or well exemplified. Although it provides a technical reference of available classes and methods, it lacks detailed explanations and practical examples showing how to call endpoints or implement common workflows. The structure assumes prior familiarity with Telegram’s internal architecture, which makes it difficult for developers to understand how to use the APIs without relying on third-party resources or community libraries. Methods such as `messages.getHistory` and TDLib’s `getMessage` illustrate this lack of clarity, as they do not present expected outputs or practical usage scenarios.

21.2.3.4 UGC_OC10: Does the platform’s documentation include or link to the API or data access terms of use?

Region	Answer	Note
BR	✅ Yes	The terms of service are explicitly referenced in the Telegram API documentation and are required reading for developers when obtaining api_id credentials.
EU	✅ Yes	The terms of service are explicitly referenced in the Telegram API documentation and are required reading for developers when obtaining api_id credentials.
UK	✅ Yes	The terms of service are explicitly referenced in the Telegram API documentation and are required reading for developers when obtaining api_id credentials.

21.2.3.5 UGC_OC11: Does the platform’s API documentation detail the response format of each endpoint?

Region	Answer	Note
BR	❌ No	The Telegram and TDLib API documentation does not consistently specify the response format for each endpoint. Although object schemas and return types are defined, the documentation often lacks explicit response examples and per-endpoint error code descriptions. Methods such as `messages.getHistory` in the Telegram API and `getMessage` in TDLib illustrate this inconsistency, as they do not provide clear examples of expected responses or error-handling details.
EU	❌ No	The Telegram and TDLib API documentation does not consistently specify the response format for each endpoint. Although object schemas and return types are defined, the documentation often lacks explicit response examples and per-endpoint error code descriptions. Methods such as `messages.getHistory` in the Telegram API and `getMessage` in TDLib illustrate this inconsistency, as they do not provide clear examples of expected responses or error-handling details.
UK	❌ No	The Telegram and TDLib API documentation does not consistently specify the response format for each endpoint. Although object schemas and return types are defined, the documentation often lacks explicit response examples and per-endpoint error code descriptions. Methods such as `messages.getHistory` in the Telegram API and `getMessage` in TDLib illustrate this inconsistency, as they do not provide clear examples of expected responses or error-handling details.

21.2.3.6 UGC_OC12: Does the platform provide its API documentation in the official languages of the assessed region?

Region	Answer	Note
BR	❌ No	The Telegram API documentation is available only in English.
EU	❌ No	The Telegram API documentation is available only in English.
UK	✅ Yes	The Telegram API documentation is available in English.

21.2.3.7 UGC_OC13: Does the platform’s API documentation detail the quota or rate limits applicable to each available endpoint?

Region	Answer	Note
BR	❌ No	While Telegram provides general information on bot rate limits, the TDLib documentation does not clearly or comprehensively specify quotas or rate limits for each data extraction endpoint.
EU	❌ No	While Telegram provides general information on bot rate limits, the TDLib documentation does not clearly or comprehensively specify quotas or rate limits for each data extraction endpoint.
UK	❌ No	While Telegram provides general information on bot rate limits, the TDLib documentation does not clearly or comprehensively specify quotas or rate limits for each data extraction endpoint.

21.2.3.8 UGC_OC14: Does the platform provide a way to label content that has been generated with artificial intelligence?

Region	Answer	Note
BR	❌ No	We found no official policy or technical specification for AI-generated content in Telegram’s API documentation and terms of service.
EU	❌ No	We found no official policy or technical specification for AI-generated content in Telegram’s API documentation and terms of service.
UK	❌ No	We found no official policy or technical specification for AI-generated content in Telegram’s API documentation and terms of service.

21.2.4 Completeness

21.2.4.1 UGC_OC15: Can data from a publication’s comments be extracted using the platform’s API?

Region	Answer	Note
BR	✅ Yes	Telegram allows extracting comments data from channels that have discussion features enabled. Each comment is treated as a reply within a message thread and can be retrieved as structured data.
EU	✅ Yes	Telegram allows extracting comments data from channels that have discussion features enabled. Each comment is treated as a reply within a message thread and can be retrieved as structured data.
UK	✅ Yes	Telegram allows extracting comments data from channels that have discussion features enabled. Each comment is treated as a reply within a message thread and can be retrieved as structured data.

21.2.4.2 UGC_OC16: Can data from temporary content be extracted through the platform’s API?

Region	Answer	Note
BR	✅ Yes	Telegram allows extracting temporary content from groups and channels while it remains available, even if messages are set with an auto-delete timer. Messages are only removed after the timer expires, but during their active period they can be accessed through the API as regular messages or stories.
EU	✅ Yes	Telegram allows extracting temporary content from groups and channels while it remains available, even if messages are set with an auto-delete timer. Messages are only removed after the timer expires, but during their active period they can be accessed through the API as regular messages or stories.
UK	✅ Yes	Telegram allows extracting temporary content from groups and channels while it remains available, even if messages are set with an auto-delete timer. Messages are only removed after the timer expires, but during their active period they can be accessed through the API as regular messages or stories.

21.2.4.3 UGC_OC17: Can historical data be extracted through the platform’s API?

Region	Answer	Note
BR	✅ Yes	Telegram's TDLib and core API allow the extraction of historical data without any fixed time limitation, including content older than one year.
EU	✅ Yes	Telegram's TDLib and core API allow the extraction of historical data without any fixed time limitation, including content older than one year.
UK	✅ Yes	Telegram's TDLib and core API allow the extraction of historical data without any fixed time limitation, including content older than one year.

21.2.4.4 UGC_OC18: Is the number of requests allowed by the API sufficient for monitoring more than 10,000 publications in 24 hours?

Region	Answer	Note
BR	✅ Yes	Telegram’s API—including TDLib and the core `messages.*` methods—does not enforce strict global rate limits that would prevent the continuous extraction of large volumes of messages, such as 10,000 posts within 24 hours.
EU	✅ Yes	Telegram’s API—including TDLib and the core `messages.*` methods—does not enforce strict global rate limits that would prevent the continuous extraction of large volumes of messages, such as 10,000 posts within 24 hours.
UK	✅ Yes	Telegram’s API—including TDLib and the core `messages.*` methods—does not enforce strict global rate limits that would prevent the continuous extraction of large volumes of messages, such as 10,000 posts within 24 hours.

21.2.5 Consistency

21.2.5.1 UGC_OC19: Are the results returned by the API consistently reproducible?

Region	Answer	Note
BR	✅ Yes	In our tests, the same request was submitted five consecutive times to the Telegram API, and identical results were returned in each case.
EU	✅ Yes	In our tests, the same request was submitted five consecutive times to the Telegram API, and identical results were returned in each case.
UK	✅ Yes	In our tests, the same request was submitted five consecutive times to the Telegram API, and identical results were returned in each case.

21.2.5.2 UGC_OC20: Is the data returned by the platform’s API consistent with the parameters and filters used in the request?

Region	Answer	Note
BR	✅ Yes	Our tests indicate that Telegram API responses are consistent with the parameters and filters specified in the requests.
EU	✅ Yes	Our tests indicate that Telegram API responses are consistent with the parameters and filters specified in the requests.
UK	✅ Yes	Our tests indicate that Telegram API responses are consistent with the parameters and filters specified in the requests.

21.2.6 Relevance

21.2.6.1 UGC_OC21: Does the data extracted by the platform’s API reflect what is displayed on its user interface?

Region	Answer	Note
BR	✅ Yes	Based on the tests conducted, requests to the Telegram API made at different times and by different researchers returned consistent data, with only minimal variation.
EU	✅ Yes	Based on the tests conducted, requests to the Telegram API made at different times and by different researchers returned consistent data, with only minimal variation.
UK	✅ Yes	Based on the tests conducted, requests to the Telegram API made at different times and by different researchers returned consistent data, with only minimal variation.

21.2.6.2 UGC_OC22: Does the platform’s API allow for filtering data based on content or its author location?

Region	Answer	Note
BR	❌ No	Telegram’s TDLib and core API do not provide parameters or endpoints that allow filtering messages or posts by the publisher’s geographic location.
EU	❌ No	Telegram’s TDLib and core API do not provide parameters or endpoints that allow filtering messages or posts by the publisher’s geographic location.
UK	❌ No	Telegram’s TDLib and core API do not provide parameters or endpoints that allow filtering messages or posts by the publisher’s geographic location.

21.2.6.3 UGC_OC23: Does the platform’s API allow for filtering data based on content language?

Region	Answer	Note
BR	❌ No	Telegram’s TDLib and core API do not include parameters or methods that enable filtering messages based on the language of their content.
EU	❌ No	Telegram’s TDLib and core API do not include parameters or methods that enable filtering messages based on the language of their content.
UK	❌ No	Telegram’s TDLib and core API do not include parameters or methods that enable filtering messages based on the language of their content.

21.2.6.4 UGC_OC24: Does the platform’s API allow for filtering data by specific time periods?

Region	Answer	Note
BR	✅ Yes	Telegram’s API, including TDLib, supports temporal filtering of messages through parameters that define retrieval ranges. The `SearchRequest` method accepts `min_date` and `max_date` parameters, allowing messages to be fetched within custom date or ID intervals. Similarly, TDLib’s `getChatHistory` method enables retrieving messages before or after a specific message ID or timestamp.
EU	✅ Yes	Telegram’s API, including TDLib, supports temporal filtering of messages through parameters that define retrieval ranges. The `SearchRequest` method accepts `min_date` and `max_date` parameters, allowing messages to be fetched within custom date or ID intervals. Similarly, TDLib’s `getChatHistory` method enables retrieving messages before or after a specific message ID or timestamp.
UK	✅ Yes	Telegram’s API, including TDLib, supports temporal filtering of messages through parameters that define retrieval ranges. The `SearchRequest` method accepts `min_date` and `max_date` parameters, allowing messages to be fetched within custom date or ID intervals. Similarly, TDLib’s `getChatHistory` method enables retrieving messages before or after a specific message ID or timestamp.

21.2.7 Timeliness

21.2.7.1 UGC_OC25: Can data from newly published content be extracted from the platform’s API in near real time?

Region	Answer	Note
BR	✅ Yes	Telegram's TDLib and core APIs support near-real-time extraction of newly published content through methods like `messages.getHistory` and `getUpdates`.
EU	✅ Yes	Telegram's TDLib and core APIs support near-real-time extraction of newly published content through methods like `messages.getHistory` and `getUpdates`.
UK	✅ Yes	Telegram's TDLib and core APIs support near-real-time extraction of newly published content through methods like `messages.getHistory` and `getUpdates`.

21.3 Advertising

Coverage: BR, EU, UK

21.3.1 Special Criteria

21.3.1.1 AD_SC1: Does the platform provide an API to access its ad repository and extract data on advertising content for independent analysis?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.1.2 AD_SC2: Does the platform provide a graphical user interface to its ad repository for extracting advertising content data?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.1.3 AD_SC3: Can data from both active and inactive ads be extracted?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.2 Accessibility

21.3.2.1 AD_OC1: Does the platform provide a GUI for accessing and visualizing its ad repository?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.2.2 AD_OC2: Is access to the platform’s ad repository free of charge?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.2.3 AD_OC3: Can the requested data be extracted directly from the ad repository response?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.2.4 AD_OC4: Does the platform’s ad repository API provide a form of authentication that allows for renewal without the risk of data loss?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.2.5 AD_OC5: Can data from an individual ad be retrieved from the platform?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.2.6 AD_OC6: Can data from ads served by a specific advertiser be retrieved from the platform?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.2.7 AD_OC7: Can ad data be retrieved from the platform using search terms?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.2.8 AD_OC8: Does the platform use locale-neutral data representations?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.3 Completeness

21.3.3.1 AD_OC9: Does the platform provide data that allows the identification of advertisers who ran ads?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.3.2 AD_OC10: Does the platform provide data on the funders who paid for ads?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.3.3 AD_OC11: Does the platform provide data on the period during which ads were served?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.3.4 AD_OC12: Does the platform provide data on user engagement with ads?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.3.5 AD_OC13: Does the platform indicate whether ads were placed by verified or unverified advertisers?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.4 Compliance

21.3.4.1 AD_OC14: Does the platform flag ads that were removed due to violations of its guidelines or relevant legislation?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.4.2 AD_OC15: Does the platform indicate whether ad content was generated using artificial intelligence?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.4.3 AD_OC16: Is the platform’s ad repository documentation published in open access?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.4.4 AD_OC17: Is the platform’s ad repository documentation clearly written and exemplified?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.4.5 AD_OC18: Does the platform’s ad repository documentation include or link to its terms of use?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.4.6 AD_OC19: Does the platform provide its ad repository documentation in the official languages of the assessed region?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.4.7 AD_OC20: Does the platform implement a proper deprecation strategy to avoid breaking client applications while rolling out major changes in the API?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.4.8 AD_OC21: Does the platform’s ad repository API documentation detail the response format of each endpoint?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.4.9 AD_OC22: Does the platform’s ad repository API documentation detail the quota or rate limits applicable to each available endpoint?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.5 Consistency

21.3.5.1 AD_OC23: Does the data retrieved by the API reflect what is displayed on the platform’s ad repository GUI?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.5.2 AD_OC24: Are the results returned by the platform consistently reproducible?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.5.3 AD_OC25: Is the data returned by the platform consistent with the parameters and filters used in the request?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.6 Relevance

21.3.6.1 AD_OC26: Does the platform allow the use of temporal filters to retrieve data on ads?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.6.2 AD_OC27: Does the platform allow filtering advertising data by ad category?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.6.3 AD_OC28: Does the platform allow filtering advertising data by geographic location?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.7 Accuracy

21.3.7.1 AD_OC29: Does the platform provide age and gender data on the audiences of ads?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.7.2 AD_OC30: Does the platform provide subnational geographic data on the audience reached by ads?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.7.3 AD_OC31: Does the platform include data on audience targeting criteria defined by advertisers?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.7.4 AD_OC32: Does the platform provide granular volume ranges for ad impressions?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-

21.3.7.5 AD_OC33: Does the platform provide granular investment ranges for ad spending?

Region	Answer	Note
BR	❌ No	-
EU	❌ No	-
UK	❌ No	-