# Item Usages

Retrieves 1Password item usages for activity monitoring.

**Sync Type: Full Synchronisation**


## Requirements
- Before you connect Monad to 1Password, you need admin access to a 1Password account, and an appropriate plan that supports audit log access. 
- Once you have access, you need to create a Bearer token following these steps: https://support.1password.com/events-reporting/#appendix-issue-or-revoke-bearer-tokens. Ensure ***auditevents*** permissions on the token. This token is long lived.
- Once done, you need to figure out your Base URL for your account for Monad to connect to. Find more info about the same here: https://developer.1password.com/docs/events-api/servers/

## Details
Monad uses the `timestamp` as a part of the query parameters on the [API](https://developer.1password.com/docs/events-api/reference/#post-apiv2itemusages) to determine what events to display. This field is updated every time a request to get events is successful with the time of the latest event generated. If this was the first time requesting for events, a full sync of the data is performed.

## Configuration
The following configuration defines the input parameters. Each field's specifications, such as type, requirements, and descriptions, are detailed below.

#### Settings

| Setting | Type | Required | Description |
|---------|------|----------|-------------|
| Base URL | string | No | The base URL for your 1Password account. |
| Backfill Start Time | string | No | The date to start fetching data from. If not specified, no past records will be fetched. |
| API Rate Limit | object | No | Optional limit on the connector's outbound request rate to the source API. Leave blank to use the connector's default behavior. See [API Rate Limiting](../../../guides/rate-limiting) for the field format, limits, and how to choose a value. |

#### Secrets

| Secret | Type | Required | Description |
|---------|------|----------|-------------|
| Bearer Token | string | Yes | Bearer token for 1Password API. This is required to authenticate requests. |

## Related Articles

- [https://developer.1password.com/docs/events-api/reference/#post-apiv2itemusages](https://developer.1password.com/docs/events-api/reference/#post-apiv2itemusages)

## Sample Record

```json
{
  "account_uuid": "d609c0a5-24de-7c77-63e1-4a03b27d9846",
  "action": "server-fetch",
  "client": {
    "app_name": "1Password Connect",
    "app_version": "6970416",
    "ip_address": "7.217.167.124",
    "os_name": "Darwin",
    "os_version": "12",
    "platform_name": "onepassword-desktop-app",
    "platform_version": "arm64"
  },
  "item_uuid": "eb69b57c-7cfb-a4e6-d7cc-3787d80c4e77",
  "location": {
    "city": "Portland",
    "country": "Germany",
    "latitude": 90,
    "longitude": -180,
    "region": "Oregon"
  },
  "timestamp": "2025-10-22T19:59:23.04665Z",
  "used_version": 32,
  "user": {
    "email": "john.smith@example.com",
    "name": "staging",
    "type": "service_account",
    "uuid": "9f2b6473-9cc1-8321-db97-52825e20dd63"
  },
  "uuid": "96032541-785b-4822-b9fc-0221eea74330",
  "vault_uuid": "8749899c-3527-47cb-d9ba-9f7b31eb2b77"
}
```

## Sync frequency

By default this input polls approximately every 10 seconds, with each sync beginning after the previous one completes. A cron schedule configured on the pipeline overrides this cadence. See [Input Sync Frequency](../../guides/sync-frequency) for details.