🎉 OneTrust 6.22 Released!

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

👍

For more information about the release and our product updates in the OneTrust application, refer to the OneTrust 6.22 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 Updates

Assessment Automation

• Send Back Assessment (Under Review to In Progress) New Public API: Added the Send Back Assessment API, which allows users to send back a specified assessment and reduce the stage level from "Under Review" to "In Progress".
  • POST /v2/assessments/{id}/send-back New API
• Reopening Assessment (Completed to Under Review) New Public API: Added the Reopen Assessment API, which allows users to reopen specified assessments and reduce the stage level from "Completed" to "Under Review".
  • POST /v2/assessments/{id}/reopen New API

Universal Consent & Preference Management

• Submit Consent Transactions Using New Public API: Added the Consent Receipts API, which allows external applications to submit requests to store data subject consent transactions. This API can be used by all Collection Points, but the Collection Point must first be set up in OneTrust to generate a valid JWT request token.
  • POST /request/v1/consentreceipts New API
• Exclude Purposes from Double Opt-In Workflow: Updated API to include the doubleOptInExcludedPurposes attribute, which can be passed within the request body to exclude certain Purposes on the Collection Point from the Double Opt-In workflow. With this enhancement, incoming consent for excluded purposes can be placed directly in Active status without requiring additional confirmation by the data subject.
  • PUT /consentmanager/v1/collectionpoints/{collectionpointId} Updated API

General

• Update User Emails via SCIM APIs: Updated SCIM APIs with the ability to update user email addresses via SCIM using the PATCH and PUT Users APIs. With this enhancement, updates made to a user’s email address within your identity provider are now reflected within the application after the next provisioning sync.
  • PATCH /Users/{id} Updated API
  • PUT /Users/{id} Updated API