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 Consent & Preferences — Consent Receipts

The Consent Receipts APIs are used to integrate external systems and streamline the flow of consent receipt data with the OneTrust Platform. (3 operations.)

OneTrust Consent & Preferences — Consent Receipts is one of 37 APIs that OneTrust publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 3 operations across 3 paths, and defines 14 schemas. It is described by OpenAPI 3.1.0, at version 1.0.

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

3 operations 3 paths 14 schemas 3 POST

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/request/v1
Authentication
OAuth 2.0
License
Resource Areas
1

Authentication & Security 1

OneTrust Consent & Preferences — Consent Receipts declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAUTH2) using the clientCredentials flow, exposing 2 scopes.

Paths & Operations 3

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

Consent Receipts 3

The Consent Receipts APIs are used to create consent receipts from a collection point to store data subject consent.

POST
/consentreceipts
Create Consent Receipts
createConsentReceiptUsingPOST 1 param body → 200400401403404429500
POST
/consentreceipts/bulk
Create Consent Receipts in Bulk
createBulkConsentReceiptUsingPOST 1 param body → 200400401403429500
POST
/consentreceipts/identified
Create Identified Consent Receipts
createIdentifiedConsentReceiptUsingPOST 1 param body → 200400401403429500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are RequestInformation (20 properties), DsPurpose (10 properties), DsPurposeNote (4 properties), DsGeolocation (4 properties). Each schema is shown below with its type and property counts.

ConsentString
object
2 properties
DsAttachments
object
1 property
DsCustomPreference
object
3 properties
DsCustomPreferenceChoices
object
2 properties
DsGeolocation
object
4 properties
DsPreference
object
2 properties
DsPrivacyNotice
object
3 properties
DsPurpose
object
10 properties
DsPurposeNote
object
4 properties
ParentPrimaryIdentifiers
object
4 properties
ReceiptOption
object
2 properties
RequestInformation
object
20 properties 2 required
Source
object
3 properties
ConsentReceiptResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

onetrust-consent-preferences-consent-receipts-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 — 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)
OneTrust Data Use Governance — Data Catalog
Where this information came from

This is an independent, third-party profile of OneTrust Consent & Preferences — Consent Receipts, 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.