Summary of changes
| Version | Date | Type | Description | Details |
|---|---|---|---|---|
| 1.4.1 | September 2025 | Improvement | Added an account UUID property to the introspect response object. | View details |
| 1.4.0 | November 2024 | New feature | Added V2 endpoints for sign-in attempts and item usage with external user and MSP support. (Breaking change *) | View details |
| 1.3.0 | September 2024 | New feature | Added V2 audit events endpoint with external user and MSP support. (Breaking change *) | View details |
| 1.2.0 | November 2023 | New feature | Added passkey credential support to audit events. | View details |
| 1.2.0 | August 2023 | Improvement | Enhanced user details in audit event responses. | View details |
| 1.2.0 | November 2022 | New feature | Added audit events endpoint and reporting capabilities. | View details |
| 1.2.0 | March 2022 | Improvement | Added geolocation info and SSO actions. | View details |
| 1.1.0 | September 2021 | Improvement | Added internal server error handling. | View details |
| 1.1.0 | August 2021 | New feature | Added V2 introspection endpoint. (Breaking change *) | View details |
| 1.0.0 | July 2021 | Initial release | Initial public release of the 1Password Events API. | View details |
Added a new
account_UUID property to the introspect endpoint (/api/v2/auth/introspect).You can now confirm the account a bearer token was issued from. This is particularly relevant to managed service providers (MSPs) that manage multiple accounts.Added new V2 endpoints with external user and MSP functionality:
- POST /api/v2/signinattempts
- POST /api/v2/itemusages
- New SignInAttemptV2 schema:
- Added
account_uuidfield - Added
federatedsign-in type - Uses enhanced UserV2 schema
- Added
- New ItemUsageV2 schema:
- Added
account_uuidfield - Uses enhanced UserV2 schema
- Added
- New SignInAttemptUserTypes enum for user type classification
Breaking changes
V2 endpoints introduce new required fields and response structures. If upgrading from V1:- Response schemas include new required fields
- User objects now include type classification
- New enums added for MSP functionality
Migration impact
V1 endpoints continue to be supported. Migration to V2 endpoints is only required if you’re an MSP provider and you need to access MSP-related event data for your account or the accounts of your managed companies.New integrations can use V2 endpoints regardless of MSP needs.Added new V2 audit events endpoint with MSP support:
- POST /api/v2/auditevents
- New AuditEventV2 schema:
- Added
actor_typefield - Added
actor_account_uuidfield - Added
account_uuidfield
- Added
- Added AuditEventActorTypes enum
- Added new actions:
expirelaunchiunlink
- Added
mngdaccobject type for managed accounts
- Added “cred” object type for passkey authentication
- Fixed latitude field name in Location schema
Enhanced AuditEvent schema with detailed user information:
- Added
actor_details - Added
object_details - Added
aux_details
- Added audit events endpoint (/api/v1/auditevents)
- Added new schemas:
- AuditEvent
- AuditEventItems
- AuditEventActions
- AuditEventObjectTypes
- Session
- Added Location object to sign-in attempts and item usage events:
countryregioncitylongitudelatitude
- Added new item usage actions:
select-sso-providerenter-item-edit-mode
- Added 500 Internal Server Error response to all endpoints
Added V2 introspection endpoint:
- New introspection endpoint (/api/v2/auth/introspect)
- V1 endpoint marked as deprecated
- Added IntrospectionV2 schema with consistent naming
Initial public release of the 1Password Events API, including:
- Introspection endpoint
- JWT authentication
- Item usage endpoint
- Sign-in attempts endpoint
- Cursor-based pagination