POST /token/generate

Requests a UID2 token generated from a user's DII (email address or phone number). If the DII is valid, and the user has not opted out of UID2, this operation returns a UID2 token and associated values.

Used by: This endpoint is used mainly by publishers.

important

The optout_check parameter, required with a value of 1, checks whether the user has opted out.

Rather than calling this endpoint directly, you could use one of the SDKs to manage it for you. For a summary of options, see SDKs: Summary.

Request Format

POST '{environment}/v2/token/generate'

For authentication details, see Authentication and Authorization.

Here's what you need to know about sending requests to this endpoint:

• To ensure that the API key used to access the service remains secret, UID2 tokens must be generated only on the server side after authentication.
• You must encrypt all requests using your secret. For details, and code examples in different programming languages, see Encrypting Requests and Decrypting Responses.

Path Parameters

Path Parameter	Data Type	Attribute	Description
{environment}	string	Required	Testing (integration) environment: https://operator-integ.uidapi.com 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. Notes: The integ environment and the prod environment require different API keys. Token expiration time is subject to change, but is always significantly shorter in the integ environment than it is in the prod environment.

Unencrypted JSON Body Parameters

important

You must include only one of the following four conditional parameters, plus the required optout_check parameter with a value of 1, as key-value pairs in the JSON body of the request when encrypting it.

Body Parameter	Data Type	Attribute	Description
email	string	Conditionally Required	The email address for which to generate tokens.
email_hash	string	Conditionally Required	The Base64-encoded SHA-256 hash of a normalized email address.
phone	string	Conditionally Required	The normalized phone number for which to generate tokens.
phone_hash	string	Conditionally Required	The Base64-encoded SHA-256 hash of a normalized phone number.
optout_check	number	Required	Checks whether the user has opted out. Include this parameter with a value of 1.

Request Examples

important

To ensure that the API key used to access the service remains secret, the POST /token/generate endpoint must be called from the server side, unlike POST /token/refresh which does not require using an API key. If you want to generate tokens on the client side, see Client-Side Integration Options (for web-based implementations) or UID2 Client-Side Integration Guide for Mobile.

The following are unencrypted JSON request body examples for each parameter, one of which you should include in your token generation requests:

{
    "email": "username@example.com",
    "optout_check": 1
}

{
    "email_hash": "tMmiiTI7IaAcPpQPFQ65uMVCWH8av9jw4cwf/F5HVRQ=",
    "optout_check": 1
}

{
    "phone": "+12345678901",
    "optout_check": 1
}

{
    "phone_hash": "wdN1alhrbw1Bmz49GzKGdPvGxLhCNn7n3teAOQ/FSK4=",
    "optout_check": 1
}

Here's an encrypted token generation request example for an email hash:

echo '{"email_hash": "tMmiiTI7IaAcPpQPFQ65uMVCWH8av9jw4cwf/F5HVRQ=","optout_check":1}' | python3 uid2_request.py https://prod.uidapi.com/v2/token/generate [Your-Client-API-Key] [Your-Client-Secret] 

For details, and code examples in different programming languages, see Encrypting Requests and Decrypting Responses.

Decrypted JSON Response Format

note

The response is encrypted only if the HTTP status code is 200. Otherwise, the response is not encrypted.

This section includes the following sample responses:

• Successful Response
• Optout

Successful Response

A successful decrypted response returns the user's advertising and refresh tokens for the specified email address, phone number, or the respective hash.

{
  "body": {
    "advertising_token": "A4AAAABlh75XmviGJi-hkLGs96duivRhMd3a3pe7yTIwbAHudfB9wFTj2FtJTdMW5TXXd1KAb-Z3ekQ_KImZ5Mi7xP75jRNeD6Mt6opWwXCCpQxYejP0R6WnCGnWawx9rLu59LsHv6YEA_ARNIUUl9koobfA9pLmnxE3dRedDgCKm4xHXYk01Fr8rOts6iJj2AhYISR3XkyBpqzT-vqBjsHH0g",
    "identity_expires": 1724899014352,
    "refresh_expires": 1724981814352,
    "refresh_from": 1724896314352,
    "refresh_response_key": "TS0H0szacv/F3U8bQjZwjSaZJjxZbMvxqHn1l3TL/iY=",
    "refresh_token": "AAAAAGYzgUszke2sV9CxXnxyFfUU+KDCJUCXNbj1/FVcCjvR7K07jYaWe44wxM6SOTwG7WQB4XfIcquMqH57iHUnAu1zacYf9g58BtbhKCYWTwrdpB0fSqTANBXOYy+yBnl6tLRwVv32LqRCj76D8meO4tw+MKlUAc2EoFzFNPSfZLpA3Jk4q68vH6VJH/WIuu1tulrVm5J8RZAZnmTlEcsPdjoOC6X4w3aAwiwtbeGw7yOO0immpVoC5KaXnT9olRPTlrt8F9SvebLIcqkYhvRMPpl1S89yeneyGo++RnD9qSHIrfu9To3VwYW018QuvyA15uv4No4BoAzyPuHqzQ8gAs6csWwZ7VwfYD7DSJXlQiIpwzjA2Hl8mgg/5fcXwKEJ"
  },
  "status": "success"
}

Optout

Here is an example response when the user has opted out.

{
    "status": "optout"
}

Response Body Properties

The response body includes the properties shown in the following table.

Property	Data Type	Description
advertising_token	string	An encrypted advertising (UID2) token for the user.
refresh_token	string	An encrypted token that can be exchanged with the UID2 Service for the latest set of identity tokens.
identity_expires	number	The Unix timestamp (in milliseconds) that indicates when the advertising token expires.
refresh_from	number	The Unix timestamp (in milliseconds) that indicates when the SDK for JavaScript (see SDK for JavaScript Reference Guide) will start refreshing the UID2 token. TIP: If you are not using the SDK, consider refreshing the UID2 token from this timestamp, too.
refresh_expires	number	The Unix timestamp (in milliseconds) that indicates when the refresh token expires.
refresh_response_key	string	A key to be used in a POST /token/refresh request for response decryption.

Response Status Codes

The following table lists the status property values and their HTTP status code equivalents.

Status	HTTP Status Code	Description
success	200	The request was successful. The response will be encrypted.
optout	200	The request was successful. Could not generate token because the user has opted out.
client_error	400	The request had missing or invalid parameters.
unauthorized	401	The request did not include a bearer token, included an invalid bearer token, or included a bearer token unauthorized to perform the requested operation.

If the status value is anything other than success, the message field provides additional information about the issue.

Test Identities

Type	Identity	Purpose	Next Endpoint
Email	validate@example.com	Test that the advertising_token you've cached matches the advertising_token for the specified email address.	POST /token/validate
Email	optout@example.com	Using this email for the request always generates an optout response.	POST /token/generate
Email	refresh-optout@example.com	Using this email for the request always generates an identity response with a refresh_token that results in an optout response.	POST /token/refresh
Phone	+12345678901	Test that the advertising_token you've cached matches the advertising_token for the specified phone number.	POST /token/validate
Phone	+00000000002	Using this phone number for the request always generates an optout response.	POST /token/generate
Phone	+00000000000	Using this phone number for the request always generates an identity response with a refresh_token that results in an optout response.	POST /token/refresh