Skip to main content
Account events alert you when an end-user’s stored EHR credentials need attention. They’re not tied to a specific operation — Cobalt’s authentication layer fires them when it detects a credential issue during any login attempt. There are two account events:
  • access_token.login_required — credentials are no longer valid; the user must re-authenticate via Cobalt Link before further operations can succeed.
  • access_token.password_change_warning — the EHR is prompting the user to change their password. Re-authenticate proactively to avoid an interruption.
For both, surface data.message to the affected user and direct them to Update Mode to refresh their credentials.

Identifying the credential

A connection can hold more than one set of EHR credentials, and an account event is always about exactly one of them. Both events carry credential_id, the ID of that credential set, so you do not have to guess which login needs attention. credential_id is also the ID the credential endpoints take, so you can act on the credential straight from the event: The last active credential set on a connection cannot be disabled or deleted.
credential_id is present on the envelope and repeated inside data. Treat it as nullable: in the rare case where Cobalt cannot resolve the credential set behind an event, it is null. Fall back to access_token_id to identify the connection.

Payload Envelope

Event Types

Triggered when an end-user’s stored EHR credentials are no longer valid (e.g. password changed in the EHR, account locked, or password expired). The user must re-authenticate via Cobalt Link before further operations can succeed.Payload Example:
Data Fields:
Triggered when an EHR prompts the user to change their password but the prompt was deferred. This is an early warning that a password change will be required soon.Payload Example:
Data Fields: