🎉 OneTrust 202510.2.0 Released!

We are excited to announce the following enhancements in the OneTrust Developer Portal as part of OneTrust 202510.2.0 (Fall Release).

👍

For more information about the release and our product updates in the OneTrust application, refer to the OneTrust Release Notes page. Learn more about environment maintenance on the Current and Historic Maintenance page, and subscribe to proactive environment notifications on our System Status and Scheduled Maintenance page.

Cookie Consent

New Public Preview Features

• Get List of Bulk Export Download Details API: Added the new Get List of Bulk Export Download Details API to the Bulk Export APIs to retrieve the download details for a bulk export with paginated results. This API allows you to pass the continuationToken and size parameters, optimizing response times and mitigating any possible timeout errors.

Existing Public Preview Features

• Bulk Export APIs: The following APIs are now available for use to create and cancel bulk exports and retrieve their status, progress, download details, and credit details. These APIs enable users to extract large volumes of cookie receipts at once with a limit of six bulk exports per month.
  • Create Bulk Export API
  • Get List of Bulk Exports API
  • Get Bulk Export Status API
  • Cancel Bulk Export API
  • Get Bulk Export Download Details API
  • Get Bulk Export Credit Details API

Data Subject Request (DSR) Automation

Things to Know

• Updated the Complete Subtask API to include a character limit of 1.5 million on the comment parameter. Comments added via API or directly in the platform are now limited to 1.5 million characters.

Issues Management

General Availability

• Modify Issue API: The new Modify Issue API is now available for use to partially update the details of an existing issue. This API allows you to apply minor updates to the issue, streamlining the update process and eliminating the need to perform a complete issue update.

Mobile App Consent

Existing Public Preview Features

• Consent Management Platform APIs: The following APIs are now available for use with retrieving interface attributes needed to display the Banner and Preference Center, retrieving a list of active IAB and Google Vendors to display on the Preference Center, and logging consent when an end user interacts with a Banner or Preference Center. These APIs enable you to easily access data for Banner and Preference Center implementations, disclose vendor information to end users, and capture end user consent.
  • Get Banner Data API
  • Get Preference Center Data API
  • Get IAB and Google Vendors API
  • Log Consent API
  • Get Universal Consent Purposes API

Things to Know

• The following changes have been made to the Consent Management Platform (CMP) APIs:
  • Updated the Get Banner Data, Get Preference Center Data, and Log Consent APIs to add the IABTCF_VendorsDisclosed and IABGPP_TCFEU2_VendorsDisclosed parameters within the storageKeys object of the response. This enhancement ensures compliance with the latest IAB TCF v2.3 specification.
• The new Mobile SDKs powered by the CMP API now return the latest consent given when changing regions, ensuring consistent platform behavior aligned with the Web CMP experience.

Settings & Administration

General Availability

• Users V2 APIs: The following APIs are now available for use when managing users and their assignments to roles and organizations. These APIs enable you to efficiently retrieve, create, and update users and add or remove their assignments to roles and organizations, streamlining access control and improving administrative productivity.
  • Get List of Users API
  • Create User API
  • Get User API
  • Update User API
  • Get User Roles API
  • Add User Role API
  • Remove User Role API
  • Modify User Default Organization API

Universal Consent & Preference Management

General Availability

• Get List of Bulk Export Download Details API: Added the new Get List of Bulk Export Download Details API to the Bulk Export APIs to retrieve the download details for a bulk export with paginated results. This API allows you to pass the continuationToken and size parameters, optimizing response times and mitigating any possible timeout errors.

Fixed

• Resolved an issue where the ​Get Data Subject Details API ​returned multiple privacy notice versions associated with the same purpose. A new logic has been implemented to ensure that previous notice versions are replaced by the latest applicable version.
• Resolved an issue that caused data subject identifier values to display incorrectly as “Processing…” on the ​Transactions​ tab of the ​Receipts​ screen after bulk importing consent records using the ​Create / Update Data Subject Consent​ import template. In addition, a related issue where the ​identifier​ parameter returned a ​null​ value in the response of the ​Get List of Transactions API​​ has also been resolved.
• The v4 ​Get List of Data Subject Group Members API​ now returns information about updates to data subject groups performed either through the ​Groups​​ screen on the platform or via the v2 Update Data Subject Group API.
• Resolved an issue that prevented the ​Get Data Subject Details API​​ from returning the correct privacy version after submitting an old notice version through the Create Consent Receipts API.
• The ​Get Data Subject Details API​ no longer returns details of parent data subjects when passing a data element in the ​identifier​​ header parameter.
• Resolved an issue that prevented the ​Create Consent Receipts API​ from transferring purposes after data subject merge when ​enableDataElementDateValidation​ was set to ​true​​.
• Resolved an issue where the v4 ​Get Data Subject Token API​​ returned an outdated data subject link token, while the v1 Get List of Data Subject Tokens API and the platform correctly displayed the latest token. Link tokens are now consistently aligned across API responses and the user interface.

Things to Know

• Error 500 responses returned by the v4 Data Subject APIs have been standardized to comply with established API conventions, such as OpenAPI and JSON error schema. These messages now follow a predictable format to maintain consistency.