Merge identities

Merges two identities into one. The secondary identity is folded into the primary. Per-object-type transfer toggles control which linked data is re-pointed. Tags are always merged. - Sessions linked to the secondary are re-pointed to the primary - Session counts are combined (when sessions are transferred) - Screening checks, face embeddings, IP/device links optionally transferred - Tags are merged and deduplicated - The secondary identity is marked as `merged` (or `redacted` if requested) Both identities must belong to the same organization and environment. Redacted or already-merged identities cannot be used as the secondary.

Authentication

X-API-Keystring

Organization API key. Keys are prefixed with vk_live_ (production) or vk_sandbox_ (sandbox).

Headers

Verifa-VersiondateOptional

API version date string (e.g. 2026-02-01). If omitted, the version pinned to your API key is used.

Key-InflectionenumOptionalDefaults to snake

Response key casing. Defaults to snake.

Allowed values:
Idempotency-KeystringOptional<=255 characters

Unique key for idempotent requests. Cached for 24 hours. Sending the same key with different parameters returns 422.

Request

This endpoint expects an object.
primary_identity_idstringRequired
The identity to keep.
secondary_identity_idstringRequired
The identity to merge into the primary.
transferobjectOptional

Per-object-type toggles for what to transfer. All default to true.

redact_secondarybooleanOptionalDefaults to false
If true, redact the secondary identity's PII after merge.
reasonstring or nullOptional
Optional note explaining why the merge was performed.

Response

Merge result.
primaryobject
secondaryobject
transfer_summaryobject
Which object types were transferred.
redacted_secondaryboolean
reasonstring or null

Errors

401
Unauthorized Error
404
Not Found Error
422
Unprocessable Entity Error