---
title: "List Email Messages"
method: GET
path: "/v1/teams/{team_id}/email/messages"
tags: ["operator"]
---

# List Email Messages

`GET /v1/teams/{team_id}/email/messages`

## Request

- Base URL: `https://api.stormy.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.stormy.ai/v1/teams/{team_id}/email/messages`
- Auth: none declared

Message headers across the team's mail — who wrote, which way, when.

A thread row carries a subject, a snippet and a timestamp; it cannot say
who is on the other end or how many messages it holds. Without this, a mail
list has to open all N threads to draw one screen, so the operator surface
reads this once and groups client-side exactly the way it does with calls.

Bodies are deliberately absent: their lengths answer "how much did it
contain", and the reader that needs the words asks for the single thread it
is showing. Narrower than the thread read, never wider.

## Path parameters

- `team_id` string, uuid, required

## Query parameters

- `thread_id` string, uuid, nullable
- `account_id` string, uuid, nullable
- `limit` integer
- `offset` integer

## Headers

- `authorization` string, nullable
- `x-darwin-token` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/stormy/apis/stormy-control-plane.md) · [All operations](https://skmtc.dev/stormy/apis/stormy-control-plane/llms.txt) · [OpenAPI document](https://skmtc.dev/stormy/apis/stormy-control-plane/revisions/4d811ab18158?raw)