🎉 OneTrust 202606.2.0 Released!

We are excited to announce the following enhancements in the OneTrust Developer Portal as part of OneTrust 202606.2.0.

Cookie Consent

General Availability

• 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.
  • 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
  • Get List of Bulk Export Download Details API

Data Subject Rights (DSR) Automation

Fixed

• The list of supported values for the verificationType request parameter in the Create Verification Method API has been updated to correctly reflect supported verification method types.
  • Removed: AUTOMATED, EXTERNAL
  • Added: DEFAULT, KNOWLEDGE, DOCUMENT, EMAIL, PHONE

Mobile App Consent

New Public Preview Features

• Enhancements to Consent Management Platform APIs
  The following enhancements have been made to the Consent Management Platform (CMP) APIs:

  • Updated the errors object of CMP API responses to include ERROR_CODE_EMPTY_CONSENT as a response for the code parameter and At least one purpose consent is required as a response for the message parameter. This error is returned by the Log Consent API when logging Universal Consent preferences with OT-Explicit-Consent: true and an empty payload. This enhancement adds error handling to avoid generating empty receipts and ensure that at least one consent is captured.

  Age Based Consent is now supported for the CMP APIs. The following enhancements allow you to capture and manage age range information as part of the consent flow, enabling age-based experiences within your applications.

  • Updated the Log Consent API to include AGEGATE_RANGE as a value for the interactionType request parameter and to include the new ageGate request parameter. When interactionType is set to AGEGATE_RANGE, the ageGate parameter is required to configure the necessary age range for age-based consent capture.
  • Updated the Get Banner Data API to include the linkedCategories parameter to return the list of consent categories linked to age groups within the ageGate parameter of the prompts object of the response.
  • Updated CMP API responses to include the new OT_AgeGate parameter within the storageKeys object of the response.
  • Updated the errors object of CMP API responses to include ERROR_CODE_INVALID_AGE_RANGE as a response for the code parameter and The upper bound of the age range must be greater than lower bound as a response for the message parameter.

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

Universal Consent & Preference Management

Fixed

• Resolved an issue that caused the Get List of Data Subjects V4 API to produce error messages when filtering by a consent date or withdrawal date older than the collection point's linked policy.
• The list of supported values for the sort query parameter in the Get List of Data Subjects V4 API has been updated to correctly reflect supported sort criteria. The createdDate,asc and createdDate, desc values have been removed.