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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
OneTrust

OneTrust Incidents API

APIs used to create, update, search, and manage incidents, including linking incidents to inventories, retrieving details, and tracking their lifecycle.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

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

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

7 operations 6 paths 29 schemas 1 GET5 POST1 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
Contact
OneTrust Support
License
Apache 2.0
Resource Areas
1

Authentication & Security 1

OneTrust Incidents API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAUTH2) using the clientCredentials flow, exposing 3 scopes.

Paths & Operations 7

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

Incidents 7

APIs used to create, update, search, and manage incidents, including linking incidents to inventories, retrieving details, and tracking their lifecycle.

POST
/incident/v1/assignments/entities/{entityId}/stage
Update Incident Stage
assignStageByName 1 param body → 200400401403429500
POST
/incident/v1/assignments/entities/{entityId}/types/{type}/stage
Update Incident Stage by Type
assignStageByName_1 2 params body → 200400401403429500
POST
/incident/v1/incidents
Create Incident
createIncidentUsingPOST body → 201400401403429500
POST
/incident/v1/incidents/search
Search Incidents
searchIncidentsUsingPOST 3 params body → 200400401403429500
GET
/incident/v1/incidents/{incidentId}
Get Incident
getIncidentDetailByIncidentIdUsingGET 1 param → 200400401403429500
PUT
/incident/v1/incidents/{incidentId}
Update Incident
updateIncidentUsingPUT 1 param body → 200400401403429500
POST
/incident/v1/incidents/{incidentId}/inventory-links/{inventoryType}
Link Incident to Inventory
createInventoryLinks 2 params body → 201400401403429500

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are IncidentInformation (34 properties), IncidentDetails (33 properties), IncidentListInformation (29 properties), WorkflowStageListInformation (18 properties). Each schema is shown below with its type and property counts.

IncidentAssigneeInformation
object
3 properties
IncidentInformation
object
34 properties
InventoryLinkCreationRequest
object
3 properties
StageExceptionInformation
object
3 properties
AssociatedAttributeValueInformation
object
4 properties 1 required
BasicEntityDetail
object
2 properties
SearchCriteriaInformation
object
2 properties
IncidentJurisdictionCreateRequest
object
3 properties 1 required
IncidentJurisdictionGuidanceInformation
object
14 properties
IncidentCreateRequest
object
15 properties 3 required
IncidentStatus
string
WorkflowStageAssignmentInformation
object
4 properties
InventoryLinkAssociationInformation
object
4 properties
IncidentSourceType
string
AdvanceStageActionInformation
object
3 properties 2 required
EntityOrganizationInformation
object
2 properties 1 required
IncidentAssigneeRequest
object
3 properties 1 required
AttributeValueInformation
object
8 properties 1 required
LinkCreationMode
string
NotificationNeededType
string
IncidentDetails
object
33 properties
WorkflowStageListInformation
object
18 properties 3 required
AssessmentInformation
object
4 properties 1 required
WorkflowStageApproverInformation
object
9 properties 3 required
NamedAttributeValueInformation
object
9 properties 1 required
WorkflowSpecificStageNavigationRequest
object
2 properties 1 required
IncidentUpdateRequest
object
13 properties 3 required
IncidentAttachmentResponse
object
9 properties 4 required
IncidentListInformation
object
29 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

onetrust-incidents-api-openapi.yml Raw ↑

Other APIs OneTrust publishes across the network.

OneTrust Activity Log API
AE Profile APIs.io
OneTrust Applications API
AE Profile APIs.io
OneTrust Assessment Actions API
AE Profile APIs.io
OneTrust Assessment Management API
AE Profile APIs.io
OneTrust Assessments API
AE Profile APIs.io
OneTrust Attachments API
AE Profile APIs.io
OneTrust Attachments V4 API
AE Profile APIs.io
OneTrust Attribute Management API
AE Profile APIs.io
OneTrust Audit Records API
AE Profile APIs.io
OneTrust Audits API
AE Profile APIs.io
OneTrust Banner API
AE Profile APIs.io
OneTrust Bulk Export API
AE Profile APIs.io
#Incidents
← Back to O APIs
API Details
ID
onetrust:onetrust-incidents-api
Base URL
https://app.onetrust.com
Docs
https://developer.onetrust.com/onetrust/reference/attribute-management
Provider
OneTrust
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=onetrust-incidents-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/onetrust-incidents-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of OneTrust Incidents 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.