> ## 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.

# Request headers

Requests to the Events API must include the correct header(s):

* `Authorization`: Each GET and POST request to the Events API must be [authorized with a bearer token](/events-api/authorization/) scoped to access event data for that feature. You'll include your token in the authorization header.

* `Content-Type`: Each POST request requires a `Content-Type` header 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 specify `application/json` as the content type. GET requests don't contain a request body and therefore don't require this header.

An example of a request header:

```
Authorization: Bearer YOUR_BEARER_TOKEN
Content-type: application/json
```
