/api/v3/auditevents) that uses the HTTP GET method and cursor-based pagination with query parameters. Audit events include information about the actor, the target of the action, contextual information (like where the session originated), and more.
Learn more about the v3 API conventions and how the v2 and v3 APIs compare.
Requirements
Before you get started with the beta API, you’ll need:- A 1Password Business or 1Password Enterprise Password Manager account (not included with 1Password Teams).
- Permissions to manage integrations in your 1Password account (for example, as an owner, administrator, or member of the Security group).
Step 1: Set up an Events Reporting integration
To use the API, you’ll need to set up an Events Reporting integration in your account on 1Password.com. If you’ve already set one up, you can also use an existing integration.Set up a new integration
- Sign in to your account on 1Password.com.
- Select Integrations in the sidebar. If you’ve set up other integrations in your account, you’ll also need to select Directory on the Integrations page.
- In the Events Reporting section, choose your SIEM from the list. If your SIEM isn’t listed, select Other.
- Enter a name for the integration, then select Add Integration.
- Set up a bearer token:
- Token Name: Enter a name for the token.
- Expires After: (Optional) Choose when the token will expire: 30 days, 90 days, 180 days, or Never (default).
- Events to Report: Choose which events the token can access. The default scope includes all events: sign-in attempts, item usages, and audit events. Learn more about token scopes.
- Select Issue Token.
- On the “Save your token” page, select Save in 1Password. Choose the vault where you want to save your token, then select Save.
Your bearer token will be saved as an API Credential item in 1Password. - Select View Integration Details.
Use an existing integration
If you’ve already set up an Events Reporting integration and want to use the same integration for different versions of the API, follow these steps:- Sign in to your account on 1Password.com.
- Select Integrations in the sidebar.
- Select the Events Reporting integration you want to use.
- Select Add a token to issue a new bearer token for the integration.
Or use an existing bearer token. Confirm that the integration has an active bearer token scoped to access audit events, and verify that you can access the saved token in 1Password. - Set up your new bearer token:
- Token Name: Enter a name for the token.
- Expires After: (Optional) Choose when the token will expire: 30 days, 90 days, 180 days, or Never (default).
- Events to Report: Choose which events the token can access. The default scope includes all events: sign-in attempts, item usages, and audit events. Learn more about token scopes.
- Select Issue Token.
- On the “Save your token” page, select Save in 1Password. Choose the vault where you want to save your token, then select Save.
Your bearer token will be saved as an API Credential item in 1Password. - Select View Integration Details.
Step 2: Find your Events API base URL
The/api/v3/auditevents beta endpoint currently uses the same Events API servers as the v2 production endpoint.
Choose the base URL that matches the region where your 1Password account is hosted:
You’ll use this base URL together with the v3
auditevents path. For example:
Step 3: Send a test request with curl
Use curl on the command line to send a test request and confirm your integration is working.3.1: Create a curl request
In your terminal, format your request using the following structure:<base_url>: The Events API base URL for your 1Password account. For example:https://events.1password.com.<YOUR_BEARER_TOKEN>: The bearer token for your Events Reporting integration.
? and separated by &:
max_page_size: The maximum number of events to return in a single response. If you don’t include themax_page_sizeparameter, or if you set it to0, the server default of100is used. The endpoint accepts any positive value, but it returns no more than1000events per page.start_time: The earliest insertion time for which to retrieve events (exclusive), filtered on when events were ingested by 1Password. Uses RFC 3339 format. For example:2026-01-01T00:00:00Z.end_time: The latest insertion time for which to retrieve events (exclusive), filtered on when events were ingested by 1Password. Uses RFC 3339 format. For example:2026-01-12T23:59:59Z.
start_time and end_time parameters, the endpoint will return a page of events using the service-defined default time range.
3.2: Send a curl request
The following example sends a GET request to the/api/v3/auditevents endpoint, using the curl command structure from the example above. Adjust the query parameters as needed.
--data-urlencode flags. Include the --get flag so curl adds the parameters to the URL as a query string instead of sending them in the request body.
3.3: Review the response
Review the response to confirm that theaudit_events array contains the expected event data.
Example response
audit_events array is empty), try adjusting your start_time and end_time parameters.
If there are more events available than can be returned in a single response, the beta endpoint returns an opaque next_page_token at the top level of the response. To request the next page of results, pass the next_page_token value in the page_token query parameter. For example:
next_page_token value that gets returned until the response no longer includes a token.
Learn more about pagination and continuous polling in the beta API.
Step 4: Test the beta endpoint
After you’ve confirmed your Events API integration is working, you can test the beta/api/v3/auditevents endpoint with your SIEM.