Requests to the Events API must include the correct header(s):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.
-
Authorization: Each GET and POST request to the Events API must be authorized with a bearer token scoped to access event data for that feature. You’ll include your token in the authorization header. -
Content-Type: Each POST request requires aContent-Typeheader to indicate the media type of the resource being sent in the request body. All data for the Events API is sent and received as JSON, so you’ll need to specifyapplication/jsonas the content type. GET requests don’t contain a request body and therefore don’t require this header.