We've detected that you are using the Brave browser. This site does not display correctly when the Brave Shields are enabled. Please set your Shields to Down.
OneTrust Internal Users: DO NOT MAKE ANY DIRECT CHANGES!
All documentation updates should be made by submitting a DOC ticket, and changes to the APIs should be made by opening a merge request (MR) in the SARCH (sandbox) or DX (production) GitLab Repos.
🚧 API Specification Update in Progress: We're migrating our APIs from Swagger 2.0 to OpenAPI 3.1.0. This upgrade brings improved compatibility, flexibility, and support for modern API standards. For more information, see OneTrust API Migration to OpenAPI 3.1.0.
Use this API to create a new data asset or upsert an existing data asset. Data assets must be added using a structured top-down hierarchy to ensure consistent data organization. The request must include all required data asset details, such as the parent ID, name, type, and data source. The response will confirm successful ingestion with the assigned data asset ID.
Things to Know
If terms, tags, additional attributes, or users are added to an existing data asset, the system will merge the new values from the request with the existing values.
With the exception of the root (data source) node, every data asset must have its parent record already present in the system before being added.
Responses
401
Unauthorized
403
Forbidden
404
Data Asset Not Found
429
Too Many Requests.
For more information, see API Rate Limits.