Skip to main content
An identity event records one change that Lumos detected on an identity: which field changed, its old and new values, and when Lumos detected the change. A user is one kind of identity. A status change, a new email address, and an identity joining a group each produce an event. A change to two fields at once produces two events. Events are read-only. You read them through one endpoint, List Identity Events.
The Identity Event object

Attributes

A group membership change shows the group’s name, and a custom attribute change shows the attribute’s value.

Who can read identity events

Of the built-in roles, Admin and Read Only Admin can list identity events.

Filtering

List Identity Events returns events newest first, by detected_time. Four filters narrow the list: changed_fields matches labels exactly, including case, so Status works and status returns 400. The built-in labels are Given Name, Family Name, Full Name, Email, Status, Identity Type, Email Is Lumos Generated, Identity Source App, and Group Membership. Any other label must be the label of one of your custom attributes. A label that matches neither returns 400, and the error message lists the built-in labels.

Reading to the end

page_size defaults to 100 and is capped at 100. Every page with events has a next_page_token, including the last one, so the request after the last page returns no events, and its next_page_token is missing or null. A page can also be empty while next_page_token is still set. Short and empty pages explains when to stop.

Endpoints