Merge Identities

Developing

POST

https://api.lootlocker.com/identity/v1/merge

Merges merge_identity_id into the authenticated session identity and keeps the authenticated identity.

The merge identity is tombstoned, its credentials and player links move to the kept identity, its sessions are revoked, and the merge is written to identity_merge_log. Every game in which both identities have a live player must carry a resolution naming the player to keep; the other player of that game is soft-deleted. A missing or invalid resolution answers 400 and writes nothing.

This is destructive and never runs automatically. Get the conflicts from POST /identity/v1/merge/preview (or the merge offer of the request that met the conflict) and let the player choose.

Requires a game session (x-session-token) that is linked to an identity.

Request

Authorization

API Key

Add parameter in header

x-session-token

Example:

x-session-token: ********************

Body Params application/jsonRequired

Examples

Responses

🟢200Success

application/json

The surviving identity.

Bodyapplication/json

🟠400Rejected request

🟠404Identity not found

🔴500Unexpected error

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://api.lootlocker.com/identity/v1/merge' \
--header 'x-session-token: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
    "merge_identity_id": "string",
    "resolutions": [
        {
            "game_id": 0,
            "keep_player_id": 0
        }
    ],
    "trigger_provider": "string",
    "trigger_provider_uid": "string"
}'

Response Example

200 - Example 1

{
    "id": "string",
    "publisher_id": 0,
    "created_at": "2019-08-24T14:15:22.123Z",
    "game_activity": [
        {
            "game_id": 0,
            "first_session_at": "2019-08-24T14:15:22.123Z",
            "last_session_at": "2019-08-24T14:15:22.123Z",
            "session_count": 0
        }
    ]
}

Modified at 2026-10-22 13:10:01

Preview Identity Merge

Metadata Value