🎉 OneTrust 202606.1.0 Released!

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

👍

For more information about the release and our product updates in the OneTrust Platform, 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

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

Incident Management

General Availability

• Enhancements to Incidents APIs
  The following enhancements have been made to the Incidents APIs:
  • Updated the Get Incident API and Update Incident API to include the attributeName parameter within the attributeValues object of the response. This enhancement enables clearer identification and mapping of returned attributes.
  • Updated the behavior of the Update Incident API. Previously, if existing attribute values were not included in the request, they would be overwritten by empty values. With this enhancement, existing attribute values will no longer be overwritten and will now be retained even if those attribute values are not included in the request.

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 Log Consent API to include the OT-Explicit-Consent header parameter to allow sending only explicit consent choices rather than consent to all purposes tied to the CMP collection point. When OT-Explicit-Consent: true, consent will be logged only for the purpose for which consent was updated. When OT-Explicit-Consent: false, consent will be logged for all purposes.

    This parameter is currently only supported for the UC_PREFERENCE_CENTER_CONFIRM interaction type.

  • Updated the Get Universal Consent Purposes API to include the lastConsentedDate response parameter. The lastConsentedDate will be returned for each purpose for which consent was given.
  • Updated the Get Universal Consent Purposes API to include the following parameters within the storageKeys object of the response:
    • OT_GroupConsents
    • OT_GroupLIConsents
    • OT_SdkConsents
    • OT_GeneralVendorsConsents
    • OT_LastConsentedDate
  • Updated the Get Banner Data, Log Consent, and Get Preference Center Data APIs to include the OT_UCPConsents parameter within the storageKeys object of the response.
  • Updated the consent transaction types sent when logging Universal Consent preferences using the Log Consent API.
    • For first-time consent:
      • If consent is given for a purpose with or without options selected, the transaction type will be CONFIRMED.
      • If consent is not given for a purpose, the transaction type will be OPT_OUT.
    • If consent was previously given for a purpose and is given again, the transaction type will be CONFIRMED.
    • If consent was previously given for a purpose but is later removed, the transaction type will be WITHDRAWN.
    • If consent was previously given for a purpose and the user modifies topics or custom fields, the transaction type will be CHANGE_PREFERENCES.

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

General Availability

• Search for Data Subjects by Data Element
  The following new APIs are now available for use when searching for data subjects using a specific data element:

  • ​The Create Custom Index API and Get Index Creation Status API are now available to manage the creation of custom search indexes for data elements. These APIs allow you to trigger the creation of a custom index to optimize search performance using the indexed data element value.
  • The new Search Data Subjects by Data Element API is now available to search for data subjects based on a specific data element name and value. This API allows you to quickly locate and manage data subjects based on their stored data element attributes.

  This enhancement delivers faster, more scalable consent retrieval to return the consent status for a family account and its associated child identifiers, reducing front-end complexity and improving performance.

Fixed

• Resolved an issue that caused the Get List of Receipts API to display a 400 error when a receipt lookup was performed for a data subject identifier that did not exist. The API now returns "content": [] for non-existent identifiers.