# Get Warmup Stats

> Aggregate warmup numbers across the workspace.

Requires an API key with the `read` scope.

## Response

<ResponseField name="data" type="object">
  Totals.

  <Expandable title="data">
    <ResponseField name="totalAccounts" type="integer">Email accounts in the workspace.</ResponseField>
    <ResponseField name="activeWarmupAccounts" type="integer">Accounts with warmup on.</ResponseField>
    <ResponseField name="totalSent" type="integer">Warmup emails sent by the workspace's accounts.</ResponseField>
    <ResponseField name="totalReplied" type="integer">Warmup replies counted across the workspace's accounts.</ResponseField>
    <ResponseField name="averageHealthScore" type="number">Average Health Score over warming accounts that have one, to one decimal. `null` while none do.</ResponseField>
    <ResponseField name="healthMeasuredAccounts" type="integer">How many accounts the average covers.</ResponseField>
  </Expandable>
</ResponseField>

<RequestExample>
```bash cURL
curl -X GET "https://api.foxreach.io/api/v1/warmup/stats" \
  -H "X-API-Key: otr_your_key"
```

```python Python SDK (beta)
from foxreach import FoxReach

client = FoxReach(api_key="otr_your_key")
stats = client.warmup.get_stats()
```

```typescript TypeScript SDK (beta)
import { FoxReach } from "foxreach";

const client = new FoxReach({ apiKey: "otr_your_key" });
const stats = await client.warmup.stats();
```
</RequestExample>

<ResponseExample>
```json
{
  "data": {
    "totalAccounts": 5,
    "activeWarmupAccounts": 4,
    "totalSent": 1280,
    "totalReplied": 1104,
    "averageHealthScore": 91.5,
    "healthMeasuredAccounts": 4
  }
}
```
</ResponseExample>

## Errors

| Status | Description |
|--------|-------------|
| `401` | Missing, invalid, revoked or expired API key |
| `403` | API key does not have the required scope: `read` |

## Rate Limit

- **100 requests per minute, per API key.** Fixed 60-second window.
- Every response includes `X-RateLimit-Limit`, `X-RateLimit-Remaining`, and `X-RateLimit-Reset` (unix epoch seconds).
- A `429` response includes a `Retry-After` header (seconds until the bucket resets).

For client-side patterns (`Retry-After`, exponential backoff, monitoring `X-RateLimit-Remaining`), see [Rate Limiting](/rate-limiting).