# Get account send rate limit usage

Returns outbound send rate limit consumption (messages and recipients) and mailbox, address and domain creation churn over the rolling 24-hour window for an account.

## `GET /api/v1/accounts/{accountId}/send-usage`

### Path parameters

- `accountId` (string, required) — Account ULID identifier

### Responses

**200** — Current window send limit usage and effective account caps

`application/json` → AccountSendUsage

- `accountId` (string, required) — Account ULID
- `burstWindowSeconds` (integer <int64>, required) — Width of one burst bucket in seconds (3600); the burst figures cover two of them
- `creates` (object, required)
  - `addresses` (integer | null, required) — Addresses (routes) created in the rolling 24-hour window, one per new address (a re-create of the same address does not count again); 0 while addressesPerDay is null, since nothing is counted while that limit is off; null = the count could not be read right now (the rest of the answer is unaffected; read again)
  - `addressesPerDay` (integer | null, required) — Maximum addresses allowed to be created per day (null = unenforced: the account's number is 0, or MAX_ADDRESS_CREATES_PER_DAY is blank, which switches the limit off)
  - `domains` (integer | null, required) — Domain onboardings counted in the rolling 24-hour window: one per new domain name POSTed, counted before the ownership check, so an onboarding that fails verification counts and a re-POST of the same name does not; 0 while domainsPerDay is null, since nothing is counted while that limit is off; null = the count could not be read right now (the rest of the answer is unaffected; read again)
  - `domainsPerDay` (integer | null, required) — Maximum domains allowed to be onboarded per day (null = unenforced: the account's number is 0, or MAX_DOMAIN_CREATES_PER_DAY is blank, which switches the limit off)
  - `mailboxes` (integer <int64>, required) — Mailboxes created in the rolling 24-hour window
  - `perDay` (integer | null, required) — Maximum mailboxes allowed to be created per day (null = unenforced)
- `send` (object, required)
  - `messages` (integer <int64>, required) — Distinct messages sent in the rolling 24-hour window, plus each accepted list post whose fan-out is still being delivered: the count the daily limit is checked against
  - `messagesHour` (integer <int64>, required) — Distinct messages in the BURST window (current + previous hourly bucket), summed across the account's ledger shards
  - `msgsPerDay` (integer | null, required) — Configured daily message limit (null = unenforced)
  - `msgsPerHour` (integer | null, required) — Configured hourly (burst) message limit (null = unenforced)
  - `rcptsPerDay` (integer | null, required) — Configured daily recipient limit (null = unenforced)
  - `rcptsPerHour` (integer | null, required) — Configured hourly (burst) recipient limit (null = unenforced)
  - `recipients` (integer <int64>, required) — Total recipients sent to in the rolling 24-hour window, plus the recipients an accepted list post still holds for its fan-out: the count the daily limit is checked against
  - `recipientsHour` (integer <int64>, required) — Recipients in the BURST window (current + previous hourly bucket)
- `sendHold` ("disabled" | "paused" | null, required) — The account's own hold: 'disabled' = permanent stop, 'paused' = reversible hold, null = neither
  - _option 1: "disabled" | "paused"_
  - _option 2: null_
  - _option 3: null_
- `windowSeconds` (integer <int64>, required) — Duration of the rate-limit window in seconds (e.g. 86400)

**401** — unauthorized: the bearer credential is missing, malformed, expired, or revoked. Carries a `WWW-Authenticate: Bearer` challenge

`application/json` → ErrorBody

**404** — Account not found or not accessible to this principal

`application/json` → ErrorBody

**503** — temporary_failure: the platform's storage could not answer just now; retry after the Retry-After window. Any operation can answer this. A write that got it may have been applied, so retry it with the same idempotency key where it takes one, or read the state back first (see Transient failures in the API description)

`application/json` → ErrorBody

### Example request

```bash
curl -X GET 'https://api.open.email/api/v1/accounts/{accountId}/send-usage' \
  -H 'Authorization: Bearer oek_…'
```

## TypeScript SDK

[`openemail.accounts.getSendUsage`](/docs/sdks/typescript/accounts/get-send-usage)

```ts
const accountSendUsage = await openemail.accounts.getSendUsage(accountId)
```
