Skip to main content

Identity change audit trail​

Changes to which accounts belong to whom and to who owns what, newest first: canonical identity links and unlinks (by a person, a reviewer's decision, or the matcher merging groups), person links, canonical identity deletions, and entity ownership changes. Each entry is written in the same transaction as its change and names who made it (a person id, "matcher", or "system"). With subject_id, only the changes concerning that identity (a canonical identity, an account, an owned entity, or an owner). No total is reported.

Query Parameters
  • subject_id string

    Only the changes concerning this identity.

  • limit integer

    Possible values: >= 1 and <= 100

    The maximum number of items to return. Maximum value is 100.

  • cursor string

    Opaque pagination token returned by a previous request (next_cursor, prev_cursor or last_cursor). Omit it to fetch the first page.

Header Parameters
  • SlashID-OrgID string required

    The organization ID

    Example: af5fbd30-7ce7-4548-8b30-4cd59cb2aba1
Responses

One page of changes

Schema
  • result object[]
  • id string
  • occurred_at date-time
  • actor string

    Who made the change - a person id, "matcher", or "system".

  • change string

    Possible values: [identity_linked, identity_unlinked, canonical_identity_deleted, person_linked, person_unlinked, ownership_upserted, ownership_removed]

    What an identity change audit entry records.

  • subject_ids string[]

    Every identity the change concerns.

  • details object

    The change's particulars (mapping type, ownership type and source, owner, reason).

  • meta object
  • pagination object
  • limit integer
  • offset integer
  • total_count int64
  • cursor_pagination object

    Cursors are opaque. Follow the tokens the server returns; never construct, parse or modify one.

  • limit integer
  • next_cursor string

    Opaque token addressing the next page. Absent on the last page.

  • prev_cursor string

    Opaque token addressing the previous page. Absent on the first page.

  • last_cursor string

    Opaque token addressing the final page directly, so a client can jump to the end without a total count.

  • total_count int64

    Total number of matching items. Returned on the FIRST page only; clients cache it for the remainder of the walk.