---
search:
  tags:
    - Emails
    - GET
seo:
  description: >-
    Get email metrics. Reference for the GET /emails/metrics endpoint in the
    BillionSend API.
sidebar:
  label: Get email metrics
  badge: GET
title: Get email metrics
type: openapi-operation
---
`GET /emails/metrics`

**Responses**

- `200` — Email metrics for the range, as totals and, when dimensions are given, one row per combination. Counts come from statistics written within seconds of the events; \`received\` is the accepted-for-sending count and is left out of answers scoped or broken down by domain, broadcast or email. Rates are percentages. Counts cover whole UTC hours: \`start\_date\` is floored to its hour, the whole hour of \`end\_date\` counts, and the response shows the start used. Dates before 1970 read as 1970. \`timezone\` must be an IANA name such as \`Europe/Berlin\` or \`UTC\`, not a UTC offset. \`sent\` counts recipients, like \`delivered\`, \`bounced\` and \`complained\`, so the rates stay at or under 100%. \`email\` rows list up to 1,000 emails created in the range when no email\_id is given. A key held to one domain always reads that domain only.
- `401` — Missing, malformed, unknown or revoked API key
- `403` — Restricted API key: a sending\_access key, or a key held to one domain that named another domain in domain\_id
- `422` — Validation error
- `429` — Over the rate limit (rate\_limit\_exceeded, with Retry-After)
- `503` — The statistics store is not answering; sending is unaffected. Retry shortly.

Response example, 200:

```json
{
  "object": "metrics",
  "start_date": "string",
  "end_date": "string",
  "metrics": [
    "string"
  ],
  "dimensions": [
    "string"
  ],
  "granularity": "hourly",
  "totals": {
    "property1": 0,
    "property2": 0
  },
  "data": [
    {
      "property1": "string",
      "property2": "string"
    }
  ]
}
```
