# Compliance Activities

Ingests Anthropic compliance activity events for audit trail analysis and security monitoring.

**Sync Type: Incremental**

## Requirements

Before configuring this input, you need to:

1. **Create a Compliance Access Key** — [Anthropic docs](https://docs.anthropic.com/en/docs/build-a-system/system-prompts#accessing-the-data-management-api).
    - Log in to your Anthropic account
    - Navigate to the Data Management Settings
    - Create a new Compliance Access Key
    - Ensure the key has the `read:compliance_activities` scope
    - Copy and securely store the generated key

2. **Identify Organization IDs** (optional):
    - You can filter activities by specific Anthropic organization IDs
    - If not specified, activities for all accessible organizations will be fetched
    - Organization IDs are in the format: `org_xxxxxxxx`

## Details

Monad keeps track of the state of the input via a timestamp using the `created_at.gt` filter parameter on the [Compliance Activities API](https://docs.anthropic.com/en/api/compliance). The timestamp of the last successful run is used to retrieve only newer activities that have appeared since the previous sync. Monad generates a timestamp when initiating the sync and will only save it if no errors occur during the sync.

For the first run, if no backfill start time is specified, the input defaults to a 90-day lookback window using the `created_at.gte` parameter. This ensures you capture historical compliance activities without needing to manually specify a start date.

## 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 |
|---------|------|----------|-------------|
| Backfill Start Time | string | No | Date to start fetching data from (ISO 8601 format). If not specified, defaults to a 90-day lookback window on the first sync. All subsequent syncs will be incremental. |
| Organization IDs | string | No | Comma-separated list of Anthropic organization IDs to fetch compliance activities for. If not specified, compliance activities for all organizations accessible by the provided access key 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 |
|--------|------|----------|-------------|
| Compliance Access Key | string | Yes | Compliance Access Key with `read:compliance_activities` scope. Created in Data Management Settings. |

## Rate Limits

| Scope | Limit | Window | Notes |
|-------|-------|--------|-------|
| API Requests | 2,000 | Per request | Maximum records returned per page is 2,000 |

**Headers**: `x-api-key`

**Source**: [Anthropic Compliance API Documentation](https://docs.anthropic.com/en/api/compliance)

## Related Articles

- [Anthropic API Documentation](https://docs.anthropic.com/en/docs)
- [Anthropic Compliance API Reference](https://docs.anthropic.com/en/api/compliance)
- [Data Management Settings](https://docs.anthropic.com/en/docs/build-a-system/system-prompts#accessing-the-data-management-api)

## Sample Record

```json
{
  "id": "activity_123456",
  "created_at": "2025-03-18T14:30:45.123Z",
  "organization_id": "org_12345678",
  "organization_uuid": "550e8400e29b41d4a716446655440000",
  "actor": {
    "type": "user_actor",
    "email_address": "user@example.com",
    "user_id": "user_abcdefgh",
    "ip_address": "192.0.2.1",
    "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36"
  },
  "type": "claude_chat_created",
  "claude_chat_id": "claude_chat_550e8400e29b",
  "claude_project_id": null
}
```

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