---
title: "Get identity history for a person"
method: GET
path: "/v5/persons/{person_id}/identity-history"
tags: ["Persons"]
---

# Get identity history for a person

`GET /v5/persons/{person_id}/identity-history`

Returns the chronological log of identity-merge and identity-link events for the specified person. Each entry records the event type, the previous identity key information, and the event date. Use this to audit how a person's unified profile evolved over time.

## Path parameters

- `person_id` string, required

## Response `200`

Successful response

- IdentityLogResponse[]
  - union
    - object
      - `log_date` string, required — [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) or [RFC 9557](https://datatracker.ietf.org/doc/html/rfc9557#section-4) date-time with a numeric [UTC offset](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) and an optional [IANA time-zone](https://datatracker.ietf.org/doc/html/rfc9557#section-4) suffix in square brackets. Precision up to milliseconds.
      - `old_identity_key_name` string, required — Name of the identity key before the change. Absent if not applicable.
      - `old_identity_key_value` string, required — Value of the identity key before the change. Absent if not applicable.
      - `type` 'IDENTITY_SHIFT', required — Type of identity event (`IDENTITY_SHIFT` or `SPLIT_LOSER`).
      - `identity_profile_update_version` integer, required — Version number of the identity profile after the shift. Absent for older entries.
      - `identity_shape_shift_type` 'ANONYMOUS_NO_KEY' | 'ANONYMOUS_WITH_KEY' | 'DEVICE_AND_IDENTITY_MERGED' | 'DEVICE_AND_IDENTITY_WITH_DIFFERENT_KEY' | 'DEVICE_AND_IDENTITY_WITH_KEY' | 'DEVICE_MERGED' | 'DEVICE_NO_KEY' | 'DEVICE_NO_KEY_IDENTITY_WITH_KEY' | 'DEVICE_WITH_DIFFERENT_KEY' | 'DEVICE_WITH_KEY' | 'IDENTITY_MERGED' | 'IDENTITY_WITH_KEY', required — The specific type of identity shape shift that occurred.
    - object
      - `log_date` string, required — [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) or [RFC 9557](https://datatracker.ietf.org/doc/html/rfc9557#section-4) date-time with a numeric [UTC offset](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) and an optional [IANA time-zone](https://datatracker.ietf.org/doc/html/rfc9557#section-4) suffix in square brackets. Precision up to milliseconds.
      - `old_identity_key_name` string, required — Name of the identity key before the change. Absent if not applicable.
      - `old_identity_key_value` string, required — Value of the identity key before the change. Absent if not applicable.
      - `type` 'SPLIT_LOSER', required — Type of identity event (`IDENTITY_SHIFT` or `SPLIT_LOSER`).
      - `losing_identity_key_value` string, required — Identity key value of this (losing) profile before the split. Absent if not applicable.
      - `winning_identity_id` string, required — Extole person id of the winning (surviving) profile. Absent if not applicable.
      - `winning_identity_key_name` string, required — Identity key name of the winning (surviving) profile after the split. Absent if not applicable.
      - `winning_identity_key_value` string, required — Identity key value of the winning (surviving) profile after the split. Absent if not applicable.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `402` — Payment Required
- `403` — Forbidden
- `415` — Unsupported Media Type
- `429` — Too Many Requests

---

[API](https://skmtc.net/extole/apis/integration-api-server-to-extole.md) · [All operations](https://skmtc.net/extole/apis/integration-api-server-to-extole/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/extole/integration-api-server-to-extole/versions/c16e62e66755/schema)