🎉 OneTrust 202509.1.0 Released!

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

👍

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

Existing Public Preview Features

Data Subject Request (DSR) Automation

General Availability

  • New Parameter for Update Request Custom Fields API: The Update Request Custom Fields API has been updated to include the mapOptionKeyToNameKey query parameter. This parameter allows users to map form field option keys with their respective form field name keys.

Fixed

  • Resolved an issue that prevented the Create Verification Method API from processing correctly when the translate query parameter was missing a value. The defaultValue is now set to false.

Incident Management

General Availability

  • Link Incident to Inventory API: The Link Incident to Inventory API was added to enable users to link an incident with a specific inventory type. This helps users to easily associate various inventory types (like assets, processing activities, vendors, or entities) with an incident by using inventory IDs or external identifiers.

IT Risk Management

Fixed

  • Resolved an issue that prevented the Get List of Linked Risks API from returning results when the includeHierarchicalChildInventoryRisks parameter was included in the request.

Mobile App Consent

Existing Public Preview Features

Universal Consent & Preference Management

Fixed

  • Resolved an issue that prevented v1 and v2 of the Get Data Subject’s Preferences API from returning the correct data element values after updating a data subject’s data element via the Create Consent Receipts API. If a data element is updated passing enableDataElementDateValidation = true and the interaction date is earlier than today, the data subject now retains the previous value of the data element. On the contrary, if no interaction date is provided, the current date is used, and the new value is applied.
  • Resolved an issue that prevented the Get List of Data Subject Group Members API from returning all the members belonging to a data subject group in the response.