# Send later, reply text, invites and files

> Schedule a message with send_at, read the new text of a reply without the quoted history, answer calendar invitations and read text from attached files.

Source: https://trotta.email/docs/mail-features

Four things mail needs, each with the guard on top: what is screened is screened when it counts.

## Send later

Add `send_at` to any send: a new message, `/send`, a reply, a forward, or `POST /v1/messages/{id}/send` on a draft. An ISO 8601 time with its offset, 30 seconds to 30 days ahead.

```bash
curl -X POST https://api.trotta.email/v1/inboxes/inb_7Qh2mXc4/messages \
  -H "Authorization: Bearer $TROTTA_MAIL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"to": "jordan@trotta.email", "subject": "Quarterly review",
       "text": "Here are the numbers for Friday.", "send_at": "2026-11-19T09:00:00-08:00"}'
```

- It waits as `scheduled`, in the Scheduled folder and its conversation. Event `message.scheduled`.
- When due it goes through the same checks as mail sent now: screening, write levels, approval, plan limits. As whoever scheduled it, as they are then.
- Refused then, it returns to drafts with `schedule_failed`. Event `message.schedule_failed`.
- A key that only writes drafts cannot schedule: `403 agent_drafts_only`.
- `POST /v1/messages/{id}/cancel_schedule` stops it. `POST /v1/messages/{id}/send` sends it now. It never goes twice.

## Reply text

`extracted_text` is the new part of a message: no quoted history, no signature. It comes from the safe text, so what the guard removed stays removed.

A reply, as read:

```json
{
  "text": "Friday works.\n\n-- \nJordan Ellis\n\nOn Mon, Nov 18, 2026, Riley <riley@trotta.email> wrote:\n> Can we review on Friday?",
  "extracted_text": "Friday works."
}
```

Six languages, Outlook headers, `>` quotes, and the quote blocks Gmail, Apple Mail and Outlook put in HTML. A forward keeps what it forwards. `/v1/threads/{id}/context` gives earlier messages as their new part only.

## Calendar invitations

Invitations are read on arrival, inline or as `.ics` files, into `extracted.events`. Times keep their zone. The title, place, description and organizer name are screened like a subject: in the safe view a field that carried an instruction is `null`.

extracted.events[0]:

```json
{
  "uid": "q4-review@trotta.email", "method": "REQUEST", "status": "CONFIRMED",
  "summary": "Quarterly review", "location": "Room 4",
  "start": "2026-11-20T10:00:00-08:00", "end": "2026-11-20T10:30:00-08:00",
  "all_day": false, "timezone": "America/Los_Angeles",
  "organizer": { "address": "jordan@trotta.email", "name": "Jordan Ellis" },
  "attendee_count": 3, "sequence": 0, "response": null
}
```

Answer one. The reply goes to the organizer through the normal send path, screened like any mail.

```bash
curl -X POST https://api.trotta.email/v1/messages/msg_8Kd2pXw1/rsvp \
  -H "Authorization: Bearer $TROTTA_MAIL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"response": "accepted", "comment": "See you there."}'
```

## Attachment text

Text is read from PDF, Word, Excel, PowerPoint and OpenDocument files on arrival. The guard screens it, so an instruction hidden in a document holds the message for an agent, and a secret in a document an agent sends is refused. Attachments carry `has_text` and `pages`.

```bash
curl "https://api.trotta.email/v1/messages/msg_8Kd2pXw1/attachments/att_4Hs9qLe2/text" \
  -H "Authorization: Bearer $TROTTA_MAIL_API_KEY"
```

The safe view is the default: instructions aimed at an AI are taken out. `?view=full` needs a human or `mail:full`. Held and sealed mail follow the message's rules.

Files are read as hostile: at most 15 MB, 50 pages and 200,000 characters, archive limits on size, entries and compression, a time budget, and no file can fail a delivery.
