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 Inventory Relationships V2 API

The Inventory Relationships V2 APIs are used to manage V2 inventory relationships.

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

Tagged areas include Inventory Relationships V2. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

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

12 operations 10 paths 25 schemas 2 DELETE2 GET4 POST4 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
License
Resource Areas
1

Authentication & Security 1

OneTrust Inventory Relationships V2 API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAUTH2) using the clientCredentials flow, exposing 1 scope.

Paths & Operations 12

Across 10 paths, the API surfaces 12 operations — 2 DELETE, 2 GET, 4 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Inventory Relationships V2 12

The Inventory Relationships V2 APIs are used to manage V2 inventory relationships.

POST
/api/inventory-linking/v1/contextual-entities/inventory/{inventoryId}/pages
Get List of Relationships
listAllInventoryRelationshipsUsingPOST 4 params body → 200400401403429500
PUT
/api/inventory-linking/v1/contextual-entities/{contextualLinkId}/contextual-entity-types/names/{entityTypeName}
Update Relationship by Type Name
updateInventoryRelationsUsingEntityTypeName_1 2 params body → 200400401403429500
PUT
/api/inventory-linking/v1/contextual-entities/{contextualLinkId}/contextual-entity-types/names/{entityTypeName}/data-elements
Link or Unlink Personal Data to Relationship by Type Name
linkOrUnlinkInventoryRelationshipsUsingRelationshipUsingPUT_1 2 params body → 201400401403429500
POST
/api/inventory-linking/v1/contextual-entities/{contextualLinkId}/contextual-entity-types/names/{entityTypeName}/data-elements/pages
Get Personal Data for Relationship by Type Name
getPersonalDataForRelationshipsUsingPOST_1 5 params body → 200400401403429500
PUT
/api/inventory-linking/v1/contextual-entities/{contextualLinkId}/contextual-entity-types/{entityTypeId}
Update Relationship by Type ID
updateInventoryRelationsUsingEntityTypeName 2 params body → 200400401403429500
PUT
/api/inventory-linking/v1/contextual-entities/{contextualLinkId}/contextual-entity-types/{entityTypeId}/data-elements
Link or Unlink Personal Data to Relationship by Type ID
linkOrUnlinkInventoryRelationshipsUsingRelationshipUsingPUT 2 params body → 201400401403429500
POST
/api/inventory-linking/v1/contextual-entities/{contextualLinkId}/contextual-entity-types/{entityTypeId}/data-elements/pages
Get Personal Data for Relationship by Type ID
getPersonalDataForRelationshipsUsingPOST 5 params body → 200400401403429500
POST
/api/inventory-linking/v1/inventories/relations
Create Relationship
createInventoryRelationsUsingPOST body → 201400401403429500
GET
/api/inventory-linking/v1/relationship-types/names/{relationshipTypeName}/relationship/{relationshipId}
Get Relationship by Type Name
getInventoryRelationshipUsingRelationshipTypeName_1 2 params → 200400401403429500
DELETE
/api/inventory-linking/v1/relationship-types/names/{relationshipTypeName}/relationship/{relationshipId}
Delete Relationship by Type Name
deleteInventoryRelationsUsingRelationshipTypeName_1 2 params → 204400401403429500
GET
/api/inventory-linking/v1/relationship-types/{relationshipTypeId}/relationship/{relationshipId}
Get Relationship by Type ID
getInventoryRelationshipUsingRelationshipTypeName 2 params → 200400401403429500
DELETE
/api/inventory-linking/v1/relationship-types/{relationshipTypeId}/relationship/{relationshipId}
Delete Relationship by Type ID
deleteInventoryRelationsUsingRelationshipTypeName 2 params → 204400401403429500

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are BaseContextualEntityInformation (11 properties), RelationshipTypeInformation (8 properties), AttributeValueInformation (8 properties), RelationshipInformation (7 properties). Each schema is shown below with its type and property counts.

RelationshipType
object
3 properties
LinkRequestDto
object
6 properties 4 required
SearchCriteria
object
3 properties
EntityListRequest
object
3 properties
PersonalDataLinkRequest
object
2 properties
AttributePredicate
object
4 properties 1 required
AssociatedAttributeValueInformation
object
4 properties 1 required
AttributeQueryCriteria
object
2 properties
InventoryIdentifier
object
5 properties
RelationshipTypeInformation
object
8 properties
BaseContextualEntityInformation
object
11 properties
ContextInformation
object
1 property
EntityQueryRequest
object
4 properties
DateDto
object
2 properties
RelationshipInformation
object
7 properties
FilterInformation
object
4 properties 1 required
AttributeValueInformation
object
8 properties 1 required
BasePersonalDataResponse
object
5 properties 3 required
EntityFieldRequest
object
4 properties 1 required
BasicEntityIdAndName
object
2 properties
RelationshipLabelInformation
object
3 properties
ContextualLinkUpdateRequest
object
2 properties
EntityIdAndType
object
2 properties 2 required
PersonalDataDetailedResponse
object
6 properties
ObjectReference
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

onetrust-inventory-relationships-v2-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 Inventory Relationships V2 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.