How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

OneTrust Risk Actions API

APIs to manage risk workflow actions including submissions, approvals, exceptions, and stage transitions within the risk lifecycle.

OneTrust Risk Actions API is one of 138 APIs that OneTrust publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Risk Actions. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 7 operations across 7 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://{hostname}.

7 operations 7 paths 21 schemas 7 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://app.onetrust.com
Authentication
OAuth 2.0, OAuth 2.0, OAuth 2.0
License
Resource Areas
1

Authentication & Security 3

OneTrust Risk Actions API declares 3 security schemes for authenticating requests. It supports OAuth 2.0 (TechRiskCompliance-ITRiskManagement_OAUTH2) using the clientCredentials flow, exposing 2 scopes. It supports OAuth 2.0 (TechRiskCompliance-RiskTemplate_OAUTH2) using the clientCredentials flow, exposing 3 scopes. It supports OAuth 2.0 (TechRiskCompliance-Risk_OAUTH2) using the clientCredentials flow, exposing 3 scopes.

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 7 PUT. Each is listed below with its method, path, parameters, and response codes.

Risk Actions 7

APIs to manage risk workflow actions including submissions, approvals, exceptions, and stage transitions within the risk lifecycle.

PUT
/api/risk/v2/risks/{riskId}/actions/{action}
Perform Risk Action
performRiskActionUsingPUT 2 params → 200400401403429500
PUT
/api/risk/v2/risks/{riskId}/approve
Approve Risk
approveRiskUsingPUT 1 param body → 200400401403429500
PUT
/api/risk/v2/risks/{riskId}/grant-exception
Grant Risk Exception
grantRiskExceptionUsingPUT 1 param body → 200400401403429500
PUT
/api/risk/v2/risks/{riskId}/reopen
Reopen Risk
reopenRiskUsingPUT 1 param body → 200400401403429500
PUT
/api/risk/v2/risks/{riskId}/request-exception
Request Risk Exception
requestRiskExceptionUsingPUT 1 param body → 200400401403429500
PUT
/api/risk/v2/risks/{riskId}/send-back
Send Back Risk
sendBackRiskUsingPUT 1 param body → 200400401403429500
PUT
/api/risk/v2/risks/{riskId}/submit
Submit Risk
submitRiskUsingPUT 1 param body → 200400401403429500

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are TechRiskCompliance-Risk_RiskInformation (70 properties), TechRiskCompliance-Risk_RiskLevelDetails (14 properties), TechRiskCompliance-Risk_EntityTypeInformation (9 properties), TechRiskCompliance-Risk_RiskGrantExceptionRequest (8 properties). Each schema is shown below with its type and property counts.

TechRiskCompliance-Risk_RiskGrantExceptionRequest
object
8 properties 1 required
TechRiskCompliance-Risk_AttributeValueInformation
object
8 properties 1 required
TechRiskCompliance-Risk_InventoryInformation
object
6 properties
TechRiskCompliance-Risk_BasicStageDetailTranslation
object
5 properties
TechRiskCompliance-Risk_BasicEntityDetail
object
2 properties
TechRiskCompliance-Risk_RiskInformation
object
70 properties
TechRiskCompliance-Risk_EntityTypeInformation
object
9 properties 1 required
TechRiskCompliance-Risk_RiskLevelDetails
object
14 properties
TechRiskCompliance-Risk_RiskSendBackRequest
object
1 property
TechRiskCompliance-Risk_RiskExceptionRequest
object
1 property
TechRiskCompliance-Risk_BasicStageApproverDetails
object
5 properties
TechRiskCompliance-Risk_RiskReopenRequest
object
4 properties
TechRiskCompliance-Risk_VulnerabilityInformation
object
3 properties
TechRiskCompliance-Risk_RiskSourceInformation
object
5 properties 2 required
TechRiskCompliance-Risk_RiskApproveRequest
object
8 properties 3 required
TechRiskCompliance-Risk_BasicEntityDetailTranslation
object
4 properties
TechRiskCompliance-Risk_AssociatedAttributeValueInformation
object
4 properties 1 required
TechRiskCompliance-Risk_ThreatInformation
object
3 properties
TechRiskCompliance-Risk_RiskReferenceInformation
object
5 properties
TechRiskCompliance-Risk_RiskSubmitRequest
object
1 property
TechRiskCompliance-Risk_RiskCategoryInformation
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

onetrust-risk-actions-api-openapi.yml Raw ↑

Other APIs OneTrust publishes across the network.

OneTrust Activity Log API
OneTrust Applications API
OneTrust Assessment Actions API
OneTrust Assessment Management API
OneTrust Assessments API
OneTrust Attachments API
OneTrust Attachments V4 API
OneTrust Attribute Management API
OneTrust Audit Records API
OneTrust Audits API
OneTrust Banner API
OneTrust Bulk Export API
Where this information came from

This is an independent, third-party profile of OneTrust Risk Actions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.