You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/endpoints/post-identity-buckets.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ You must encrypt all requests using your secret. For details, and code examples
31
31
32
32
### Path parameters
33
33
34
-
| Path Parameter| Data Type| Attribute | Description |
34
+
| Path parameter| Data type| Attribute | Description |
35
35
| :--- | :--- | :--- | :--- |
36
36
|`{environment}`| string | Required | Testing (integration) environment: `https://operator-integ.uidapi.com`<br/>Production environment: The best choice depends on where your users are based. For information about how to choose the best URL for your use case, and a full list of valid base URLs, see [Environments](../getting-started/gs-environments.md). |
37
37
@@ -45,7 +45,7 @@ The integration environment and the production environment require different <Li
45
45
You must include the following parameter as a key-value pair in the JSON body of a request when encrypting it.
46
46
:::
47
47
48
-
| Body Parameter| Data Type| Attribute | Description | Format |
48
+
| Body parameter| Data type| Attribute | Description | Format |
49
49
| :--- | :--- | :--- | :--- | :--- |
50
50
|`since_timestamp`| date-time or integer | Required | Specify the date and time to which to compare the last updated UTC timestamps of the buckets to be returned. | ISO 8601 format:<br/>`YYYY-MM-DDThh:mm:ss`|
51
51
@@ -106,7 +106,7 @@ The response body includes the properties shown in the following table.
106
106
107
107
The following table lists the `status` property values and their HTTP status code equivalents.
108
108
109
-
| Status | HTTP Status Code| Description |
109
+
| Status | HTTP status code| Description |
110
110
| :--- | :--- | :--- |
111
111
|`success`| 200 | The request was successful. The response will be encrypted. |
112
112
|`client_error`| 400 | The request had missing or invalid parameters. |
Copy file name to clipboardExpand all lines: docs/endpoints/post-identity-map-v2.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ You must encrypt all requests using your secret. For details, and code examples
48
48
49
49
### Path parameters
50
50
51
-
| Path Parameter| Data Type| Attribute | Description |
51
+
| Path parameter| Data type| Attribute | Description |
52
52
| :--- | :--- | :--- | :--- |
53
53
|`{environment}`| string | Required | Testing (integration) environment: `https://operator-integ.uidapi.com`<br/>Production environment: The best choice depends on where your users are based. For information about how to choose the best URL for your use case, and a full list of valid base URLs, see [Environments](../getting-started/gs-environments.md). |
54
54
@@ -62,7 +62,7 @@ The integration environment and the production environment require different <Li
62
62
You must include only **one** of the following four conditional parameters as a key-value pair in the JSON body of the request when encrypting it.
63
63
:::
64
64
65
-
| Body Parameter| Data Type| Attribute | Description |
65
+
| Body parameter| Data type| Attribute | Description |
66
66
| :--- | :--- | :--- | :--- |
67
67
|`email`| string array | Conditionally Required | The list of email addresses to be mapped. |
68
68
|`email_hash`| string array | Conditionally Required | The list of [Base64-encoded SHA-256](../getting-started/gs-normalization-encoding.md#email-address-hash-encoding) hashes of [normalized](../getting-started/gs-normalization-encoding.md#email-address-normalization) email addresses to be mapped. |
@@ -192,7 +192,7 @@ If some identifiers have opted out from the UID2 ecosystem, the opted-out identi
192
192
193
193
The response body includes the properties shown in the following table.
194
194
195
-
| Property | Data Type| Description |
195
+
| Property | Data type| Description |
196
196
| :--- | :--- | :--- |
197
197
|`identifier`| string | The email address, phone number, or respective hash specified in the request body. |
198
198
|`advertising_id`| string | The corresponding advertising ID (raw UID2). |
@@ -202,7 +202,7 @@ The response body includes the properties shown in the following table.
202
202
203
203
The following table lists the `status` property values and their HTTP status code equivalents.
204
204
205
-
| Status | HTTP Status Code| Description |
205
+
| Status | HTTP status code| Description |
206
206
| :--- | :--- | :--- |
207
207
|`success`| 200 | The request was successful. The response will be encrypted. |
208
208
|`client_error`| 400 | The request had missing or invalid parameters.|
Copy file name to clipboardExpand all lines: docs/endpoints/post-identity-map.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,7 +48,7 @@ You must encrypt all requests using your secret. For details, and code examples
48
48
49
49
### Path parameters
50
50
51
-
| Path Parameter| Data Type| Attribute | Description |
51
+
| Path parameter| Data type| Attribute | Description |
52
52
| :--- | :--- | :--- | :--- |
53
53
|`{environment}`| string | Required | Testing (integration) environment: `https://operator-integ.uidapi.com`<br/>Production environment: The best choice depends on where your users are based. For information about how to choose the best URL for your use case, and a full list of valid base URLs, see [Environments](../getting-started/gs-environments.md). |
54
54
@@ -62,7 +62,7 @@ The integration environment and the production environment require different <Li
62
62
Include one or more of the following four parameters as key-value pairs in the JSON body of the request when encrypting it.
63
63
:::
64
64
65
-
| Body Parameter| Data Type| Attribute | Description |
65
+
| Body parameter| Data type| Attribute | Description |
|`email`| string array | Conditionally Required | The list of email addresses to be mapped. |
68
68
|`email_hash`| string array | Conditionally Required | The list of [Base64-encoded SHA-256](../getting-started/gs-normalization-encoding.md#email-address-hash-encoding) hashes of [normalized](../getting-started/gs-normalization-encoding.md#email-address-normalization) email addresses to be mapped. |
@@ -166,7 +166,7 @@ Response:
166
166
167
167
The response body includes one or more of the properties shown in the following table.
|`u`| string | The raw UID2 corresponding to the email or phone number provided in the request. |
182
182
|`p`| string | One of the following:<ul><li>If the current raw UID2 was rotated in the last 90 days: the previous raw UID2.</li><li>Otherwise: `null`.</li></ul> |
@@ -188,15 +188,15 @@ The raw UID2 does not change before the refresh timestamp. After the refresh tim
188
188
189
189
For unsuccessfully mapped input values, the mapped object includes the properties shown in the following table.
|`e`| string | The reason for being unable to map the DII to a raw UID2. One of two possible values:<ul><li>`optout`</li><li>`invalid identifier`</li></ul> |
194
194
195
195
### Response status codes
196
196
197
197
The following table lists the `status` property values and their HTTP status code equivalents.
198
198
199
-
| Status | HTTP Status Code| Description |
199
+
| Status | HTTP status code| Description |
200
200
| :--- | :--- | :--- |
201
201
|`success`| 200 | The request was successful. The response will be encrypted. |
202
202
|`client_error`| 400 | The request had missing or invalid parameters. |
@@ -226,12 +226,12 @@ The following sections provide general information and guidance for migrating to
226
226
227
227
The following table shows key differences between the versions.
Copy file name to clipboardExpand all lines: docs/endpoints/post-optout-status.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ You must encrypt all requests using your secret. For details, and code examples
38
38
39
39
### Path parameters
40
40
41
-
| Path Parameter| Data Type| Attribute | Description |
41
+
| Path parameter| Data type| Attribute | Description |
42
42
| :--- | :--- | :--- | :--- |
43
43
|`{environment}`| string | Required | Testing (integration) environment: `https://operator-integ.uidapi.com`<br/>Production environment: The best choice depends on where your users are based. For information about how to choose the best URL for your use case, and a full list of valid base URLs, see [Environments](../getting-started/gs-environments.md). |
44
44
@@ -50,7 +50,7 @@ The integration environment and the production environment require different <Li
50
50
51
51
There is a single body parameter.
52
52
53
-
| Body Parameter| Data Type| Attribute | Description |
53
+
| Body parameter| Data type| Attribute | Description |
54
54
| :--- | :--- | :--- | :--- |
55
55
|`advertising_ids`| string array | Required | The list of raw UID2s for which you want to check the opt-out status.<br/>Include a maximum of 5,000 entries in one API call. |
56
56
@@ -115,7 +115,7 @@ The response body includes the following properties.
115
115
116
116
The following table lists the status property values and their HTTP status code equivalents.
117
117
118
-
| Status | HTTP Status Code| Description |
118
+
| Status | HTTP status code| Description |
119
119
| :--- | :--- | :--- |
120
120
|`success`| 200 | The request was successful. The response will be encrypted. |
121
121
|`client_error`| 400 | The request had missing or invalid parameters. |
Copy file name to clipboardExpand all lines: docs/endpoints/post-token-generate.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ Here's what you need to know about sending requests to this endpoint:
34
34
35
35
### Path parameters
36
36
37
-
| Path Parameter| Data Type| Attribute | Description |
37
+
| Path parameter| Data type| Attribute | Description |
38
38
| :--- | :--- | :--- | :--- |
39
39
|`{environment}`| string | Required | Testing (integration) environment: `https://operator-integ.uidapi.com`<br/>Production environment: The best choice depends on where your users are based. For information about how to choose the best URL for your use case, and a full list of valid base URLs, see [Environments](../getting-started/gs-environments.md).<br/>Notes:<ul><li>The `integ` environment and the `prod` environment require different <Linkhref="../ref-info/glossary-uid#gl-api-key">API keys</Link>.</li><li>Token expiration time is subject to change, but is always significantly shorter in the `integ` environment than it is in the `prod` environment.</li></ul> |
40
40
@@ -44,7 +44,7 @@ Here's what you need to know about sending requests to this endpoint:
44
44
You must include only **one** of the following four conditional parameters as key-value pairs in the JSON body of the request when encrypting it.
45
45
:::
46
46
47
-
| Body Parameter| Data Type| Attribute | Description |
47
+
| Body parameter| Data type| Attribute | Description |
48
48
| :--- | :--- | :--- | :--- |
49
49
|`email`| string | Conditionally Required | The email address for which to generate tokens. |
50
50
|`email_hash`| string | Conditionally Required | The [Base64-encoded SHA-256](../getting-started/gs-normalization-encoding.md#email-address-hash-encoding) hash of a [normalized](../getting-started/gs-normalization-encoding.md#email-address-normalization) email address. |
@@ -118,7 +118,7 @@ Here is an example response when the user has opted out.
118
118
119
119
The response body includes the properties shown in the following table.
120
120
121
-
| Property | Data Type| Description |
121
+
| Property | Data type| Description |
122
122
| :--- | :--- | :--- |
123
123
|`advertising_token`| string | An encrypted advertising (UID2) token for the user. |
124
124
|`refresh_token`| string | An encrypted token that can be exchanged with the UID2 Service for the latest set of identity tokens. |
@@ -131,7 +131,7 @@ The response body includes the properties shown in the following table.
131
131
132
132
The following table lists the `status` property values and their HTTP status code equivalents.
133
133
134
-
| Status | HTTP Status Code| Description |
134
+
| Status | HTTP status code| Description |
135
135
| :--- | :--- | :--- |
136
136
|`success`| 200 | The request was successful. The response will be encrypted. |
137
137
|`optout`| 200 | The request was successful. Could not generate token because the user has opted out. |
@@ -142,7 +142,7 @@ If the `status` value is anything other than `success`, the `message` field prov
| Email |`validate@example.com`| Test that the `advertising_token` you've cached matches the `advertising_token` for the specified email address. |[POST /token/validate](post-token-validate.md)|
148
148
| Email |`optout@example.com`| Using this email for the request always generates an `optout` response. |[POST /token/generate](post-token-generate.md)|
Copy file name to clipboardExpand all lines: docs/endpoints/post-token-refresh.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ Here's what you need to know about this endpoint:
35
35
36
36
### Path parameters
37
37
38
-
| Path Parameter| Data Type| Attribute | Description |
38
+
| Path parameter| Data type| Attribute | Description |
39
39
| :--- | :--- | :--- | :--- |
40
40
|`{environment}`| string | Required | Testing (integration) environment: `https://operator-integ.uidapi.com`<br/>Production environment: The best choice depends on where your users are based. For information about how to choose the best URL for your use case, and a full list of valid base URLs, see [Environments](../getting-started/gs-environments.md).<br/>Notes:<ul><li>The `integ` environment and the `prod` environment require different <Linkhref="../ref-info/glossary-uid#gl-api-key">API keys</Link>.</li><li>Token expiration time is subject to change, but is always significantly shorter in the `integ` environment than it is in the `prod` environment.</li></ul> |
41
41
@@ -95,7 +95,7 @@ An error response might look like the following:
95
95
96
96
The response body includes the properties shown in the following table.
97
97
98
-
| Property | Data Type| Description |
98
+
| Property | Data type| Description |
99
99
| :--- | :--- | :--- |
100
100
|`advertising_token`| string | The <Linkhref="../ref-info/glossary-uid#gl-uid2-token">UID2 token</Link> (also known as advertising token) for the user. |
101
101
|`refresh_token`| string | An encrypted token that can be exchanged with the UID2 Service for the latest set of identity tokens. |
@@ -108,7 +108,7 @@ The response body includes the properties shown in the following table.
108
108
109
109
The following table lists the `status` property values and their HTTP status code equivalents.
110
110
111
-
| Status | HTTP Status Code| Description |
111
+
| Status | HTTP status code| Description |
112
112
| :--- | :--- | :--- |
113
113
|`success`| 200 | The request was successful and a new UID2 token, with associated values, is returned in the response. The response is encrypted. |
114
114
|`optout`| 200 | The user opted out. This status is returned only for authorized requests. The response is encrypted. |
Copy file name to clipboardExpand all lines: docs/endpoints/post-token-validate.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ You must encrypt all requests using your secret key. For details, and code examp
29
29
30
30
### Path parameters
31
31
32
-
| Path Parameter| Data Type| Attribute | Description |
32
+
| Path parameter| Data type| Attribute | Description |
33
33
| :--- | :--- | :--- | :--- |
34
34
|`{environment}`| string | Required | Testing (integration) environment: `https://operator-integ.uidapi.com`<br/>Production environment: The best choice depends on where your users are based. For information about how to choose the best URL for your use case, and a full list of valid base URLs, see [Environments](../getting-started/gs-environments.md). |
35
35
@@ -44,7 +44,7 @@ Here are some key points about using this endpoint:
44
44
- Include only one of the following four valid options, as listed in the Body Parameter table: `email`, `email_hash`, `phone`, or `phone_hash`.
45
45
- Include the required body parameters as key-value pairs in the JSON body of the request when encrypting it.
46
46
47
-
| Body Parameter| Data Type| Attribute | Description |
47
+
| Body parameter| Data type| Attribute | Description |
48
48
| :--- | :--- | :--- | :--- |
49
49
| `token` | string | Required | The advertising token returned by the [POST /token/generate](post-token-generate.md) response.<br/>You can only validate an advertising token that has been generated with your own credentials.
50
50
|`email`| string | Conditionally Required | The email address for token validation. You can use any valid email value, normalized or not. |
@@ -112,15 +112,15 @@ A successful decrypted response returns a boolean value that indicates the valid
112
112
113
113
The following table provides information about the response body.
114
114
115
-
| Property | Data Type| Description |
115
+
| Property | Data type| Description |
116
116
| :--- | :--- | :--- |
117
117
|`body`| boolean | A value of `true` indicates that the email address, phone number, or the respective hash specified in the request is the same as the one used to generate the advertising token.<br/>A value of `false` indicates that the email address, phone number, or the respective hash specified in the request is not the same as the one used to generated the advertising token. |
118
118
119
119
### Response status codes
120
120
121
121
The following table lists the `status` property values and their HTTP status code equivalents.
122
122
123
-
| Status | HTTP Status Code| Description |
123
+
| Status | HTTP status code| Description |
124
124
| :--- | :--- | :--- |
125
125
|`success`| 200 | The request was successful. The response will be encrypted. |
126
126
|`client_error`| 400 | The request had missing or invalid parameters. |
0 commit comments