API Documentation
Unified Consent Core API (2.0.0)
Download OpenAPI specification:Download
The Unified Consent Core API is a REST API to interact with the Osano Unified Consent platform. Before use, you must sign up at https://osano.com. You are bound by the Osano terms of service and limits placed by those terms. All interactions with the API require authentication using an Osano API key, or a Unified Consent API key in the x-osano-api-key
and x-uc-api-key
headers respectively. They are detailed in the "Authentication" section.
curl --header 'x-uc-api-key: <API_KEY>' https://uc.api.osano.com/v2/consents/check/some-subject-id
All resources are versioned according to semantic versioning with the major version being specified in the endpoints URI such as v2
.
All major versioning will maintain backwards compatibility in that major version. Resources may add new minor versions that are not specified in the URI. The minor versions will never break backward compatibility but may add new resources or enhancements. The enhancements may include new data in the schema. We will never remove data from a schema in the same major version. To prevent your scripts or applications from breaking due to newly added data, do not error on unexpected data.
We will make a best effort to notify users when we release new major versions. We will deprecate the previous major version. Major versions may have breaking changes from previous versions such as schema changes or resource removal. All users should upgrade to the new major version in a timely manner.
The Unified Consent Core API uses API keys to authenticate requests that are generated on a per-user basis. All calls require a valid, unexpired API key. There are two types of API keys that can be used with the Unified Consent Core API. They are the Osano API key and the Unified Consent API key. Routes that involve creating, updating, or merging subjects require the Osano API key. All other routes require the Unified Consent API key.
Osano API key
Osano API keys may be generated within the Osano settings -> API Keys page. You must be an admin or have the correct privileges to generate an API key.
Once generated, the API key should be included in the x-osano-api-key
header of all that involve creating, updating, or merging subjects. For example:
curl --location 'https://uc.api.osano.com/v2/subject/merge' \
--header 'x-osano-api-key: <API_KEY>' \
--header 'Content-Type: application/json' \
--data '{
"sourceSubjectId": "some-source-subject-id",
"targetSubjectId": "some-target-subject-id"
}'
Unified Consent API key
Unified Consent API keys may be generated by using the /v2/token/create
route. First gather the configId
and the customerId
from the Configuration details page. (Select the desired Configuration from the Configurations list page) For example:
curl --location 'https://uc.api.osano.com/v2/token/create' \
--header 'Content-Type: application/json' \
--data '{
"customerId": "some-customer-id",
"configId": "some-config-id"
}'
Note: Unified Consent API keys are scoped to a single Configuration, and will not work to submit consents for another Configuration
The following type describes the body of the request to create a consent. If submitting a GPC request, the actions array in the payload will be ignored and can be omitted. GPC actions are calculated internally based on the configured privacy protocols and the provided or detected geolocation:
type CreateConsentRequest = {
compliance?: {
privacyPolicy?: {
version?: string // The privacy policy version active at the time of submitting the consent
url: string // The URL of the privacy policy
}
gpc?: number // 1 if GPC is enabled, 0 otherwise
}
subject: {
verifiedId?: string // If the subject is verified, provide the subject's verified ID
anonymousId?: string // If the subject is anonymous, provide the subject's anonymous ID
}
jurisdiction?: string | null // The applicable jurisdiction for the subject. Must be one of the configured jurisdictions, or null if none are applicable. Does not affect conflict resolution if omitted, but other features such as consent search may be affected.
actions: [
{
target: string // The privacy protocol ID to submit consent for.
vendor: string // The UC configuration ID to associate with the consent.
action: string // The subject's consent choice for the privacy protocol. Possble values: 'ACCEPT' | 'REJECT' | 'UNSELECTED'
jurisdiction?: string | null // The applicable jurisdiction for the subject. Must be one of the configured jurisdictions, or null if none are applicable. Does not affect conflict resolution if omitted, but other features such as consent search may be affected. Will override the top level jurisdiction if set.
},
]
tags: string[] // Tags associated with the consent. Can be any string. Ex: ['ccpa', 'tcpa']
attributes: { [key: string]: any } // Attributes associated with the consent. `ipAddress` and `userAgent` are automatically populated, and values passed for those keys here will be overwritten.
origin?: 'api' | 'gpc' // If submitting a GPC consent, use 'gpc', otherwise use 'api'
}
Applicable jurisdictions for a UC configuration can be determined by making a request to the /v2/collections
endpoint.
To populate the target
and vendor
values for a consent it is necessary to determine the privacy protocol ID and the UC configuration ID respectively.
Finding the UC configuration ID
To find the UC configuration ID, navigate to the UC configurations page. Click on the desired configuration to open the configuration details page. Click on the "Developers" tab, revealing the Config ID.
Finding the privacy protocol ID
To find the privacy protocol ID, follow the steps above to open the desired UC configuration's details page. Click on the "Privacy Protocols" tab. From the list of privacy protocols, pick the desired privacy protocol and click the pencil icon to open the "Edit Privacy Protocol" modal. There you will find the Target ID, which is the privacy protocol ID.
Retrieves the unified consent for a subject.
Retrieves the unified consent for a subject.
Authorizations:
path Parameters
subjectRef required | string Anonymous id, verified id, or a valid session id. |
query Parameters
ref | string Enum: "subject" "session" Indicates what type of reference is provided for the subject. Supports a subject id or a session id. |
header Parameters
x-country-code-override | string Valid ISO 3166-1 country code to override the country resolution based on the IP address. |
x-region-code-override | string Valid ISO 3166-2 region code to override the region resolution based on the IP address |
Responses
Response samples
- 200
{- "unifiedConsent": {
- "subjectId": "string",
- "brandId": "string",
- "channelIds": [
- "string"
], - "compliance": {
- "privacyPolicy": {
- "version": "string",
- "url": "string"
}, - "gpc": 1
}, - "actions": [
- {
- "target": "string",
- "vendor": "string",
- "action": "string"
}
], - "attributes": null,
- "lastUpdateDate": "string",
- "lastConflictDate": "string"
}, - "conflicts": [
- {
- "type": "string",
- "resolution": "string",
- "actionsInConflict": [
- {
- "target": "string",
- "vendor": "string",
- "action": "string",
- "consentId": "string",
- "channelId": "string",
- "createdAt": "string"
}
]
}
]
}
Checks whether a subject has given consent in a co
Checks whether a subject has given consent in a configuration.
Authorizations:
path Parameters
subjectId required | string |
header Parameters
x-country-code-override | string Valid ISO 3166-1 country code to override the country resolution based on the IP address. |
x-region-code-override | string Valid ISO 3166-2 region code to override the region resolution based on the IP address |
Responses
Response samples
- 200
{- "exists": true
}
Retrieves all collections for a given configId based on jurisdiction
Uses the configId embedded in the Unified Consent API key to retrieve an aggregrate of all applicable collections of privacy protocols for a given jurisdiction. The type can either be 'draft' or 'published'. If the type is not provided, the default is 'published'. If the jurisdiction is not provided, IP geolocation is used to determine the jurisdiction.
Authorizations:
query Parameters
jurisdiction | string |
type | string Default: "published" Enum: "draft" "published" |
Responses
Response samples
- 200
{- "jurisdictions": [
- "string"
], - "collection": {
- "collectionId": "string",
- "name": "string",
- "frameworks": [
- "string"
], - "configIds": [
- "string"
], - "jurisdiction": "string",
- "created": "string",
- "updated": "string",
- "type": "string",
- "consents": [
- { }
], - "preferences": [
- { }
]
}
}
Retrieves a collection of privacy protocols
Retrieves a collection of privacy protocols by id
Authorizations:
path Parameters
collectionId required | string |
Responses
Response samples
- 200
{- "collectionId": "string",
- "name": "string",
- "frameworks": [
- "string"
], - "configIds": [
- "string"
], - "jurisdiction": "string",
- "created": "string",
- "updated": "string",
- "type": "string",
- "consents": [
- { }
], - "preferences": [
- { }
]
}
Response samples
- 200
{- "configId": "string",
- "customerId": "string",
- "name": "string",
- "domains": [
- "string"
], - "privacyPolicyUrl": "string",
- "privacyPolicyVersion": 0,
- "processingTime": 0,
- "processingUnit": "string",
- "privacyProtocols": [
- {
- "privacyProtocolId": "string",
- "name": "string",
- "type": "string",
- "integrations": [
- {
- "connection": {
- "label": "string",
- "value": "string"
}, - "operation": {
- "label": "string",
- "value": "string"
}, - "additionalFields": true,
- "fields": { },
- "protocolValue": [
- "string"
]
}
], - "enabled": true,
- "trigger": "string"
}
], - "jurisdictionLookup": "string",
- "homepageUrl": "string",
- "created": "string",
- "updated": "string",
- "helpUrl": "string",
- "frameworks": [
- "string"
], - "headings": {
- "fontFamily": "string",
- "color": "string",
- "backgroundColor": "string"
}, - "paragraphs": {
- "fontFamily": "string",
- "color": "string",
- "backgroundColor": "string"
}, - "links": {
- "fontFamily": "string",
- "color": "string",
- "backgroundColor": "string"
}, - "primaryButtons": {
- "fontFamily": "string",
- "color": "string",
- "backgroundColor": "string"
}, - "secondaryButtons": {
- "fontFamily": "string",
- "color": "string",
- "backgroundColor": "string"
}, - "gpcSignalBanner": {
- "fontFamily": "string",
- "color": "string",
- "backgroundColor": "string"
}, - "pageBackground": "string",
- "published": "string",
- "unpublishedPageId": 0,
- "publishedPageId": 0,
- "welcomePageEnabled": true
}
Create and insert a consent
Create and insert a consent
Authorizations:
header Parameters
x-country-code-override | string Valid ISO 3166-1 country code to override the country resolution based on the IP address. |
x-region-code-override | string Valid ISO 3166-2 region code to override the region resolution based on the IP address |
Request Body schema: application/json
sessionToken | string Optional session token returned by the create profile endpoint. |
required | object |
object (compliance) | |
required | Array of objects |
attributes required | object |
origin | string |
jurisdiction | string |
Responses
Request samples
- Payload
{- "sessionToken": "string",
- "subject": {
- "verifiedId": "string",
- "anonymousId": "string"
}, - "compliance": {
- "privacyPolicy": {
- "version": "string",
- "url": "string"
}, - "gpc": 1
}, - "actions": [
- {
- "target": "string",
- "vendor": "string",
- "action": "string",
- "jurisdiction": "string"
}
], - "attributes": { },
- "origin": "string",
- "jurisdiction": "string"
}
Create and insert a gpc consent
Create and insert a gpc consent
Authorizations:
header Parameters
x-country-code-override | string Valid ISO 3166-1 country code to override the country resolution based on the IP address. |
x-region-code-override | string Valid ISO 3166-2 region code to override the region resolution based on the IP address |
Request Body schema: application/json
required | object |
object (gpc-compliance) | |
attributes required | object |
jurisdiction | string |
Responses
Request samples
- Payload
{- "subject": {
- "verifiedId": "string",
- "anonymousId": "string"
}, - "compliance": {
- "gpc": 1
}, - "attributes": { },
- "jurisdiction": "string"
}
Response samples
- 201
{- "gpcActions": [
- {
- "target": "string",
- "vendor": "string",
- "action": "string",
- "jurisdiction": "string"
}
]
}
Merge subjects (an anonymous and a verified)
Merge subjects (an anonymous and a verified)
Authorizations:
header Parameters
content-type required | string Value: "application/json" The payload is a valid serialized JSON object |
Request Body schema: application/jsonrequired
sourceSubjectId required | string non-empty |
targetSubjectId required | string non-empty |
Responses
Request samples
- Payload
{- "sourceSubjectId": "string",
- "targetSubjectId": "string"
}
Response samples
- 200
"string"
Verify a subject profile
Verify a subject profile
Authorizations:
header Parameters
content-type required | string Value: "application/json" The payload is a valid serialized JSON object |
Request Body schema: application/jsonrequired
email required | string <email> non-empty |
code required | string = 6 characters |
Responses
Request samples
- Payload
{- "email": "user@example.com",
- "code": "string"
}
Response samples
- 200
{- "verifiedId": "string"
}
Sends a verification email to a subject
Sends a verification email to a subject
Authorizations:
header Parameters
content-type required | string Value: "application/json" The payload is a valid serialized JSON object |
Request Body schema: application/jsonrequired
email required | string <email> non-empty |
Responses
Request samples
- Payload
{- "email": "user@example.com"
}
Create profile verification code
Create profile verification code
Authorizations:
header Parameters
content-type required | string Value: "application/json" The payload is a valid serialized JSON object |
Request Body schema: application/jsonrequired
email required | string <email> non-empty |
Responses
Request samples
- Payload
{- "email": "user@example.com"
}
Response samples
- 201
{- "code": "string"
}
Create and insert a subject profile
Create and insert a subject profile
Authorizations:
query Parameters
resultType | string Enum: "subject" "session" |
header Parameters
content-type required | string Value: "application/json" The payload is a valid serialized JSON object |
Request Body schema: application/jsonrequired
email required | string <email> non-empty |
profile | object |
Responses
Request samples
- Payload
{- "email": "user@example.com",
- "profile": { }
}