account_recovery.started
Customer event account_recovery.started, schema version 1, delivered in the common event envelope.
| Field | Value |
|---|---|
| Event type | account_recovery.started |
| Schema version | 1 |
| Group | Other events |
| Schema ID | https://docs.keenauth.com/events/account_recovery.started.v1.json |
Payload
data.object carries at least the identifier of the affected resource in id. The other members depend on the payload mode.
Personal data
Every event carries identifiers: the affected resource in data.object, the actor in context.actor and, for user events, the user. They are personal data of the Events category, also in the default thin payload mode, which carries no e-mail address, phone number, name or IP address.
In the full payload mode data.object is the management API representation of the resource and also carries: Credentials.
Which data each category holds, how long it is kept and how it is deleted: Personal data. Do not put special category data (for example health, biometric or religious data) in metadata or other free-form fields: the full payload delivers them to your endpoint.
Example
Example event with placeholder values (payload mode thin):
{
"id": "evt_example",
"type": "account_recovery.started",
"schema_version": 1,
"environment_id": "env_example",
"occurred_at": "2026-01-01T00:00:00Z",
"recorded_at": "2026-01-01T00:00:00Z",
"seq": 1,
"data": {
"object": {
"id": "example"
}
},
"context": {}
}
All event types: Event reference.