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 Third-Party Management — Third-Party Risk Management

The Third-Party Risk Management APIs provide comprehensive functionality for managing vendor relatio nships, engagements, and contracts within the GRC ecosystem, enabling organizations to assess, monit or, and control third-party risks through engagement lifecycle management, contract administration, and customizable attribute schemas. (15 operations.)

OneTrust Third-Party Management — Third-Party Risk Management is one of 37 APIs that OneTrust publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 15 operations across 12 paths, organized into 2 resource areas, and defines 33 schemas. It is described by OpenAPI 3.1.0, at version 1.0.

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

15 operations 12 paths 33 schemas 2 DELETE5 GET1 PATCH4 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

OneTrust Third-Party Management — Third-Party Risk Management declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAUTH2) using the clientCredentials flow, exposing 2 scopes.

Paths & Operations 15

Across 12 paths, the API surfaces 15 operations — 2 DELETE, 5 GET, 1 PATCH, 4 POST, 3 PUT. They span 2 resource areas: Contracts, Engagements. Each is listed below with its method, path, parameters, and response codes.

Contracts 7

The Contracts APIs are used to manage vendor contract operations including contract creation, updates, search functionality, contract type management, and schema configuration for…

POST
/api/vendor/v1/contracts/add
Create Contract
createVendorContractUsingPOST body → 201400401403429500
GET
/api/vendor/v1/contracts/schemas
Get Contract Schema
getContractSchemaUsingGET 1 param → 200400401403429500
GET
/api/vendor/v1/contracts/types
Get List of Contract Types
fetchAllContractTypesUsingGET → 200400401403429500
POST
/api/vendor/v1/contracts/vendors/{vendorId}/contracts
Search Contracts
searchContractByVendorAndCriteriaUsingPOST 4 params body → 200400401403429500
DELETE
/api/vendor/v1/contracts/{contractId}
Delete Contract
removeVendorContractUsingDELETE 1 param → 204400401403429500
GET
/api/vendor/v1/contracts/{contractId}/contracts
Get Contract
loadVendorContractByContractIdUsingGET 2 params → 200400401403429500
PUT
/api/vendor/v1/contracts/{contractId}/vendors/{vendorId}/contracts
Update Contract
updateVendorContractUsingPUT 2 params body → 200400401403429500
Engagements 8

The Engagements APIs are used to manage vendor engagement operations including creating, retrieving, updating, and searching engagements with comprehensive attribute management, s…

GET
/api/vendor/v1/engagement-schemas
Get Engagement Schema
getEngagementSchemaUsingGET 1 param → 200400401403429500
GET
/api/vendor/v1/engagements/{engagementId}
Get Engagement
loadEngagementByEngagementIdUsingGet 1 param → 200400401403429500
PUT
/api/vendor/v1/engagements/{engagementId}
Update Engagement
updateEngagementUsingPUT 1 param body → 200400401403429500
DELETE
/api/vendor/v1/engagements/{engagementId}
Delete Engagement
removeEngagementUsingDELETE 1 param → 204400401403429500
PATCH
/api/vendor/v1/engagements/{engagementId}
Modify Engagement
updateEngagementUsingPATCH 1 param body → 200400401403429500
PUT
/api/vendor/v1/engagements/{engagementId}/status
Update Engagement Status
updateEngagementStatus 1 param body → 200400401403429500
POST
/api/vendor/v1/engagements-search
Search Engagements
loadEngagementUsingGET 3 params body → 200400401403429500
POST
/api/vendor/v1/vendor-engagements
Create Engagement
createEngagementUsingPOST body → 201400401403429500

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are EngagementListViewInformation (36 properties), AttributeInformation (36 properties), EngagementDetailInformation (34 properties), VendorContractListInformation (32 properties). Each schema is shown below with its type and property counts.

AssociatedAttributeValueInformation
object
4 properties 1 required
AttributeValueInformation
object
8 properties 1 required
ExternalEngagementUpdateRequest
object
9 properties 1 required
EngagementDetailInformation
object
34 properties
EngagementWorkflowInformation
object
7 properties
InventoryValue
object
3 properties
Key
object
5 properties 2 required
ExternalEngagementStatusUpdateRequest
object
1 property 1 required
VendorContractUpdateRequest
object
17 properties 3 required
ContractAttachmentInformation
object
10 properties
VendorContractInformation
object
25 properties
ExternalEngagementCreateRequest
object
11 properties 2 required
FilterInformation
object
4 properties 1 required
SearchCriteriaInformation
object
3 properties
EngagementListViewInformation
object
36 properties
PageEngagementListViewInformation
object
12 properties
SortObject
object
3 properties
VendorContractListInformation
object
32 properties
PageVendorContractListInformation
object
12 properties
ExternalContractCreateRequest
object
21 properties 4 required
InventoryLink
object
2 properties 1 required
ExternalEngagementPatchUpdateRequest
object
AbacBasicAssignmentInfo
object
3 properties
AssociatedAttributeInformation
object
15 properties 4 required
AttributeDomainOptionOverrideInformation
object
13 properties
AttributeFormulaDetail
object
2 properties
AttributeInformation
object
36 properties 3 required
AttributeOptionInformation
object
7 properties 1 required
AttributeOptionMetadata
object
2 properties
AttributeOptionMetadataInformation
object
8 properties
CategoryInformation
object
3 properties
IntakeQuestion
object
4 properties
ContractTypeInformation
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

onetrust-third-party-management-third-party-risk-management-openapi.json Raw ↑

Other APIs OneTrust publishes across the network.

OneTrust AI Governance — AI Governance
OneTrust Platform — Global Activity
OneTrust Consent & Preferences — Consent Interfaces
OneTrust Consent & Preferences — Consent Management Platform (CMP)
OneTrust Consent & Preferences — Consent Receipts
OneTrust Consent & Preferences — Cookie Consent
OneTrust Consent & Preferences — Cookie Consent (Swagger)
OneTrust Consent & Preferences — Cookie Domain Data
OneTrust Consent & Preferences — Cross-Device Consent
OneTrust Consent & Preferences — Mobile App Consent
OneTrust Consent & Preferences — Policy & Notice Management
OneTrust Consent & Preferences — Universal Consent & Preference Management (OAS)
Where this information came from

This is an independent, third-party profile of OneTrust Third-Party Management — Third-Party Risk Management, 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.