Skip to content

Commit 4f49e04

Browse files
Add input example
1 parent 18af9b1 commit 4f49e04

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

docs/endpoints/post-identity-map.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,12 +109,25 @@ For details, and code examples in different programming languages, see [Encrypti
109109
The response is encrypted only if the HTTP status code is 200. Otherwise, the response is not encrypted.
110110
:::
111111

112-
A successful decrypted response returns the current UID2s, previous UID2s (where applicable) and refresh timestamps for the specified email addresses, phone numbers, or their respective hashes.
112+
A successful decrypted response returns the current UID2s, previous UID2s and refresh timestamps for the specified email addresses, phone numbers, or their respective hashes.
113113

114114
The response arrays preserve the order of input arrays. Each element in the response array maps directly to the element at the same index in the corresponding request array. This ensures that results can be reliably associated with their corresponding inputs based on array position.
115115

116116
DIIs that cannot be mapped to a UID2 are mapped to an error object with the reason for unsuccessful mapping. An unsuccessful mapping occurs if the DII is considered invalid or if the DII has opted out from the UID2 ecosystem. In these cases, the response status is still "success".
117117

118+
For example, given the following input:
119+
```json
120+
{
121+
"email": [
122+
"[email protected]" // Corresponding UID2 rotated in the last 90 days
123+
"[email protected]" // Corresponding UID2 rotated more than 90 days ago
124+
"invalid email string" // Invalid identifier
125+
"[email protected]" // DII is opted out
126+
]
127+
}
128+
```
129+
130+
The resulting response will be as follows:
118131
```json
119132
{
120133
"body":{

0 commit comments

Comments
 (0)