🎉 OneTrust 6.28 Released!

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

👍

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.

❗️

API Keys created in the Integrations module prior to OneTrust 6.14 (known as Legacy API Keys) will reach end of support on January 31, 2022. Any customers leveraging these Legacy API Keys to authenticate OneTrust APIs or any integration workflows will be affected.

Customers should update any applications or webhooks leveraging these Legacy API Keys with one of the OAuth 2.0 methods OneTrust offers to prevent any interruption of service. If you are not making use of Legacy API Keys, no changes are required. For additional details, see End of Support for Legacy API Keys.

Cookie Compliance

  • View Domains IDs: Updated API to include a list of domain IDs in the response. This change provides a list of domain IDs to leverage when using the Create Cookies and Update Cookies APIs.

Universal Consent & Preference Management

  • Filter Receipts by Purpose Guid: Updated API with the new purposeGuid filter. This allows you to filter receipts to only those containing information for a specific Purpose.
  • Delete Purposes from Select Data Subjects: Updated the API to allow the deletion of up to 100 purposes from one data subject or the deletion of one purpose from 100 data subjects. This allows you to efficiently delete purposes for data subjects in increments of 100.
  • Added Parameter in Response Schema: Updated the API to include the unsubscribeAll field in the response schema. This indicates whether a data subject has opted to unsubscribe from all purposes within a Preference Center.
  • Display Correct Custom Purpose Attributes Data: Updated the API to include the attributes field in the response schema to correctly show information about Custom Purpose Attributes rather than displaying a null value. This ensures that the proper data from the collection point will be called when using the endpoint.