---
title: "Unread and per-view counts"
method: GET
path: "/api/v1/rest/email/counts"
tags: ["Email & PEC"]
---

# Unread and per-view counts

`GET /api/v1/rest/email/counts`

## Request

- Base URL: `https://api.custodo.ai`
- URL: `https://api.custodo.ai/api/v1/rest/email/counts`
- Auth: HTTP bearer

The badges a mail client shows in its rail, in one call: unread inbox mail, starred, trash, plus draft and failed-send counts, broken down by label and by mailbox. Cheaper than paging through email_search just to read a total.

**Examples**

- How much unread mail is there?
  `GET /api/v1/rest/email/counts`

## Headers

- `X-Tenant-Id` string, uuid

## Response `200`

Done. `data` is the tool’s own answer.

- RestResult
  - `ok` true, required
  - `data` unknown, required

## Other responses

- `400`: The arguments did not validate: `error.message` names the field, what it expects and what arrived.
- `401`: No API key, or one that is malformed, unknown, revoked or expired.
- `403`: The call never ran: the module is off for this organisation, the credential lacks the permission or the module, the tier does not cover it, or the tool is destructive and the key was not minted for that.
- `422`: The tool ran and refused, in a sentence of its own (`TOOL_REFUSED`): the message says what to change. Retrying the same call will not help.
- `429`: The API key has spent its minute, or its day. Every request a key makes counts. See `Retry-After`.

---

[API](https://skmtc.dev/custodo/apis/custodo-integrazioni.md) · [All operations](https://skmtc.dev/custodo/apis/custodo-integrazioni/llms.txt) · [OpenAPI document](https://skmtc.dev/custodo/apis/custodo-integrazioni/revisions/16d336d3ec2a?raw)