Identify a user
Link one of your platform users to a Dynamo (D10x) user id. The `d10xLinkId` is attached as a `d10x_link_id` query parameter on the original deep link. Send a single object or a `batch` of up to 250.
/v1.0/user/identifyAuthorization
x-api-key x-date x-signature x-api-version Your organization API key.
In: header
Request timestamp as an IMF-fixdate string (GMT, US locale) "EEE, dd MMM yyyy HH:mm:ss z", e.g. "Sun, 06 Dec 2020 12:59:11 GMT". 30-second TTL.
In: header
HMAC-SHA256(x-date, secret) as lowercase hex.
In: header
Optional for the Audience API — accepted and ignored; included for consistency with the External API (where it is required). Send 1.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
Try it
live — writes real dataKept in this tab only and signed in your browser — your secret never leaves your device.
Body (JSON)
This sends a real POST to your live organization.
Enter your key and secret to send.
curl -X POST "https://example.com/v1.0/user/identify" \ -H "Content-Type: application/json" \ -d '{ "d10xLinkId": "a1b2c3", "userId": "user_123" }'{ "message": "Signature expired"}Audience API
Push user identities, activity, properties, purchases and conversions into Dynamo.
Directly identify a user
Link a **known Dynamo (D10x) user id** to your platform user id — no deep link involved. Unlike `/v1.0/user/identify` (which resolves the user from a `d10xLinkId`), this takes the Dynamo user id directly and **force-overrides**: if your `userId` is already mapped to a different Dynamo user and the two can't be merged, the old mapping is removed and the user is re-identified with this one. Single object only — no `batch` form.