Identify user (deferred deeplink)

Same identification flow as GET, but optional device matching fields are sent in the request body.
Required inputs are still api_key and User-Agent headers.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string

Device screen size for deferred deeplink matching.

string

Client timezone for deferred deeplink matching.

string

OS version for enhanced deferred deeplink matching.

Headers
string
required

API key for authentication.

string
required

Client user agent used for deferred deeplink matching.

string

Device/platform for deferred deeplink matching (e.g. ios, android, web).

Responses

422

Validation error (e.g. invalid parameters).

500

Server error during identification.

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json