---
title: "Change flags on several messages at once"
method: POST
path: "/api/v1/rest/email/messages/bulk"
tags: ["Email & PEC"]
---

# Change flags on several messages at once

`POST /api/v1/rest/email/messages/bulk`

## Request

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

The same fields as email_set_flags — `seen`, `starred`, `trashed` — applied to up to 500 messages in one call, instead of one round trip per message. An id outside what you may see is silently skipped, never an error; `updated` says how many actually changed.

## Headers

- `X-Tenant-Id` string, uuid

## Request body

- object
  - `ids` string[], required
  - `seen` boolean
  - `starred` boolean
  - `trashed` boolean

## 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.
- `409`: The record is in a state that does not allow it — under legal hold, already sent, already closed. `error.code` says which.
- `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)