> ## Documentation Index
> Fetch the complete documentation index at: https://www.1password.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Events API beta roadmap and changelog

<Warning>
  **Beta features are not guaranteed**

  The purpose of this roadmap is to provide beta testers with information about new or improved features that are available for testing. Beta features and improvements may be added, changed, or removed at any time and are not intended to be used in production. You can use the [beta changelog](#beta-changelog) to track changes.
</Warning>

You can use the beta roadmap to track the phased rollout of new and improved features planned for the Events API. This page will be updated periodically to indicate when:

* A new or improved feature is ready for public beta testing
* A beta feature moves into production
* A planned feature is added, changed, or removed from the roadmap

## Planned features

| Feature area     | Plan                                                                           | Phase/Status | Additional information                                                                                           |
| ---------------- | ------------------------------------------------------------------------------ | ------------ | ---------------------------------------------------------------------------------------------------------------- |
| Audit events     | Create new v3 endpoint for audit events, based on updated audit logging model. | Public beta  | Beta endpoint available for testing: [`GET /api/v3/auditevents`](/events-api/beta/reference/get-v3-auditevents). |
| Audit log        | Rename Activity Log to Audit Log and update to use new audit logging model.    | Public beta  | Learn more about the [beta audit log](https://support.1password.com/audit-log/).                                 |
| Item usages      | Add item usage events to the beta.                                             | Coming soon  |                                                                                                                  |
| Sign-in attempts | Add sign-in attempt events to the beta.                                        | Coming soon  |                                                                                                                  |

## Beta changelog

This section includes information about additive and breaking changes made to the v3 Events API throughout the beta, starting from the public beta release.

### 2026-06-25

**Summary**:

* The v3 audit events endpoint has been aligned with the [API Enhancement Proposal (AEP) design standards. <Icon icon="arrow-up-right-from-square" />](https://aep.dev/) This update includes changes to continuous polling, renames several pagination parameters, flattens the response envelope, replaces the event timestamp with separate creation and ingestion times, and standardizes the error response. You'll need to update your client to adapt polling behavior and to consume the new field names and response shape.
* **Specification file**: <a href="/static/files/events-api/events-api-beta_3.0.0_2026-06-25.yaml" download>1Password Events API beta specification (3.0.0)</a>

**Details**:

* **Pagination**:
  * <Badge color="red">Breaking</Badge> The response no longer includes a `next_page_token` when there are no more results to return. Previously, the API always returned a token, including on the final page of a response and when no events were available. Polling integrations that replayed the most recent token to check for new events must now track the `insert_time` of the last received event and use it as the `start_time` on subsequent requests. Learn more about [pagination](/events-api/beta/about-v3-beta#pagination) and [continuous polling](/events-api/beta/about-v3-beta#continuous-polling) in the beta API.
  * <Badge color="red">Breaking</Badge> The `start_time` query parameter is now exclusive (previously inclusive). Only events with an `insert_time` strictly greater than `start_time` are returned.
  * <Badge color="red">Breaking</Badge> Removed the `has_more: false` flag. The end of results is now signaled by the absence of `next_page_token` in the response.
  * <Badge color="red">Breaking</Badge> The `start_time` and `end_time` query parameters now filter on `insert_time`.
  * <Badge color="red">Breaking</Badge> Renamed the `page_size` query parameter to [`max_page_size`](/events-api/beta/reference/get-v3-auditevents#query-parameters-schema) in accordance with [AEP-158. <Icon icon="arrow-up-right-from-square" />](https://aep.dev/158/) If the parameter is omitted or set to `0`, the server default of `100` will be used. The endpoint accepts any positive value, but returns no more than `1000` events per page.
  * <Badge color="red">Breaking</Badge> Renamed the `next_page_token` query parameter to [`page_token`](/events-api/beta/reference/get-v3-auditevents#query-parameters-schema). The response field is still called `next_page_token`.

* **Response shapes**:
  * <Badge color="red">Breaking</Badge> Flattened the successful response envelope, and `audit_events` and `next_page_token` are now top-level fields. The previous `data` and `meta` wrappers are no longer used.
  * <Badge color="red">Breaking</Badge> Standardized the error response on the [AEP-193 <Icon icon="arrow-up-right-from-square" />](https://aep.dev/193/) error shape: `{ "type": "...", "message": "..." }`. Replaces the previous nested `ErrorResponse` / `Error.Message` structure.

* **Date and time of events**:
  * <Badge color="red">Breaking</Badge> Removed the `timestamp` field on each audit event. Replaced with the new `create_time` and `insert_time` fields.
  * <Badge color="red">Breaking</Badge> New required `create_time` field on each [audit event](/events-api/beta/reference/get-v3-auditevents#auditeventsresponse-auditevent-object). RFC 3339 timestamp indicating when the event occurred.
  * <Badge color="red">Breaking</Badge> New required `insert_time` field on each [audit event](/events-api/beta/reference/get-v3-auditevents#auditeventsresponse-auditevent-object). RFC 3339 timestamp indicating when the event was received and stored by 1Password.

* **Event states**:
  * <Badge color="green">Additive</Badge> New `diff` element on audit events that represent a change. Returns a [`Diff` object](/events-api/beta/reference/get-v3-auditevents#auditeventsresponse-diff-object) with `type`, `new_value`, and `old_value` fields.

* **Other changes**:
  * <Badge color="red">Breaking</Badge> Renamed the `userAgent` field to `user_agent` in the [`Context` object](/events-api/beta/reference/get-v3-auditevents#auditeventsresponse-context-object) in accordance with [AEP-140 <Icon icon="arrow-up-right-from-square" />](https://aep.dev/140/), which mandates lower\_snake\_case for JSON field names.
  * <Badge color="red">Breaking</Badge> Renamed the `region` field to `region_code` in accordance with [AEP-143. <Icon icon="arrow-up-right-from-square" />](https://aep.dev/143/) Uses [Unicode CLDR region codes <Icon icon="arrow-up-right-from-square" />](https://cldr.unicode.org/), for example: `CA`, `DE`, and `US`.
  * <Badge color="red">Breaking</Badge> New required `name` property on the [`Device` object](/events-api/beta/reference/get-v3-auditevents#auditeventsresponse-device-object).
  * <Badge color="green">Additive</Badge> New optional `correlation_id` field on the [`AuditEvent` object](/events-api/beta/reference/get-v3-auditevents#auditeventsresponse-auditevent-object) for audit events that originated from the same bulk action.

### 2026-01-13

**Summary**:

* **Public release of the Events API v3 beta**. We've launched the v3 beta of the 1Password Events API. The beta introduces a new audit logging model that provides a more comprehensive view of the actions being performed in a 1Password account.
* **Specification file**: [1Password Events API specification (3.0.0)](https://i.1password.com/media/1password-events-reporting/1password-events-api_3.0.0.yaml)

**Details**:

* A new [v3 audit events beta endpoint](/events-api/beta/reference/get-v3-auditevents):  `/api/v3/auditevents`. This endpoint can return structured audit event data starting from December 1, 2025. Audit event data includes information about who performed an action, what was affected, and context about where and how the action occurred.
* A new `GET` HTTP method for audit events.
* Cursor-based pagination with query parameters for `page_size`, `start_time`, `end_time`, and `next_page_token`.
* A new [beta audit log](https://support.1password.com/audit-log/) to monitor events that happen on your team from your 1Password.com account.