Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

1Password Events (BYOK) — connector documentation

  • MCP endpoint: https://byok-onepassword-events.connectorbay.com/mcp
  • REST API: POST https://byok-onepassword-events.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-onepassword-events.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own 1Password Events 1Password Events Reporting bearer token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-onepassword-events.connectorbay.com/health · Tool schemas: https://byok-onepassword-events.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-onepassword-events · agent@connectorbay.com

What 1Password Events (BYOK) is for

1Password Events (BYOK) lets an AI assistant read your own 1Password Events data through the 1Password Events API with a key you supply (1Password Events Reporting bearer token). Read-only: 7 tools (introspect_token, list_audit_events, list_audit_events_next, list_item_usages, list_item_usages_next, list_sign_in_attempts, list_sign_in_attempts_next). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to events.1password.com, events.1password.ca, events.1password.eu. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by 1Password Events. 1Password Events and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which 1Password event feeds can my token read?"
  • "What admin actions happened in our 1Password account yesterday?"
  • "Get the next page of 1Password audit events"
  • "Which shared vault items were revealed or exported in the last day?"
  • "Get the next page of 1Password item usage events"
  • "Were there failed or blocked 1Password sign-ins this week?"

What it does

  • introspect_token: Show which event feeds (audit events, item usages, sign-in attempts) the token may read, when it was issued and the account id.
  • list_audit_events: Start reading audit events (actions by team members such as sign-ins, invitations, vault and group changes) for a time window. Returns a cursor for list_audit_events_next. Names, emails and IP addresses are not returned.
  • list_audit_events_next: Continue reading audit events from the cursor a previous list_audit_events or list_audit_events_next call returned.
  • list_item_usages: Start reading usage events for items in shared vaults (fill, reveal, secure copy, export, share) for a time window, with item and vault ids only, never item contents. Returns a cursor for list_item_usages_next.
  • list_item_usages_next: Continue reading item usage events from the cursor a previous list_item_usages or list_item_usages_next call returned.
  • list_sign_in_attempts: Start reading sign-in attempts to the account (successful and failed, with category, type, country and client app) for a time window. Returns a cursor for list_sign_in_attempts_next.
  • list_sign_in_attempts_next: Continue reading sign-in attempts from the cursor a previous list_sign_in_attempts or list_sign_in_attempts_next call returned.

BYOK key

You bring your own 1Password Events 1Password Events Reporting bearer token (https://developer.1password.com/docs/events-api/get-started/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to events.1password.com, events.1password.ca, events.1password.eu over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the 1Password Events API (events.1password.com, events.1password.ca, events.1password.eu) with a BYOK key; documentation: https://developer.1password.com/docs/events-api/reference/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by 1Password Events. 1Password Events and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your 1Password Events account.

Built for: Worldwide. Languages: English.