Get SDK Configuration

get

https://customer-my-onetrust-com.ezproxy.utas.edu.au/bannersdk/v2/applicationdata

Use this API to retrieve a list of all templates, cookie consent models, and vendor lists data for the specified mobile or OTT application in JSON format.

🚧
Before calling this API, ensure that the Mobile App data from your OneTrust tenant has been published. For more information, see Publish Changes.

Use this API to retrieve a list of all templates, cookie consent models, and vendor lists data for the specified mobile or OTT application in JSON format.

⚠️
Before You Begin
Make sure you have published the Mobile App data from your OneTrust tenant, otherwise you will not receive a success response.
For more information on publishing, please see our Publish Changes article.

Endpoint

GET https://mobile-data.onetrust.io/bannersdk/v2/applicationdata

Location Header

The location header depends on the OneTrust environment you publish from. Select from the list below based on which OT environment you're using.

OT Environment	Location Value
cookiepro	cookie-cdn.cookiepro.com
app-uk	cdn-ukwest.onetrust.com
app-au	cdn-au.onetrust.com
app-apac	cdn-apac.onetrust.com
app	cdn.cookielaw.org
app-de	cdn.cookielaw.org
app-eu	cdn.cookielaw.org
free	cdn.cookielaw.org
iapp	cdn.cookielaw.org
iapp-eu	cdn.cookielaw.org
trial	cdn.cookielaw.org
uat	cdn.cookielaw.org
uat-de	cdn.cookielaw.org

Headers

location

string

enum

required

Required value for the blob location where the JSON data is stored.

Allowed:

application

string

required

Required value for the application Id that you've configured in OneTrust Admin portal.

lang

string

required

Required value for passing a ISO 639-1 language code. Passing this value will return the back translated text for the Banner and Preference Center UI properties.The two letter ISO language code for the language you would like returned

sdkVersion

string

required

Required value for getting correct version of SDK data. This field is normally managed by the SDK... but in Postman, you need to pass it based on the current version your OT tenant(6.2.0, 6.3.0, etc).

Data-Subject-Identifier

string

Optional value for passing a custom data subject identifier value when logging consent to Universal Consent Purposes in Mobile Preference Centers.

OT-Country-Code

string

Optional value for passing a ISO 3166-2 country code. Passing this value will return a geolocation rule that matches this country code... instead of the country code auto-determined by the server.

OT-Region-Code

string

Optional value for passing a ISO 3166-2:US code. Passing this value will return a geolocation rule that matches this region code... instead of the region code auto-determined by the server. For this to work at the US state level, the OT-Country-Code param will also need to be passed as "us".

Responses

401

Unauthorized

403

Forbidden

500

The Domain or Application hasn't been published yet

Before You Begin

Endpoint

Location Header

200OK

429Too Many Requests For more information, see API Rate Limits.