---
title: "Not built yet"
description: "Listed rather than omitted."
url: "https://openemail.uk/docs/api/reference/not-yet"
area: "API"
category: "Reference"
---

# Not built yet

Listed rather than omitted.

## What is missing (not built yet)

Finding out by trying is worse than being told. None of this exists today:

- A delivery is tried up to five times: as it happens, then after 1 minute, 5, 25 and 2 hours. Every attempt is recorded and readable through `GET /webhooks/{id}/deliveries`, each carrying its `attempt` and `maxAttempts`. Retrying stops early when the answer says repeating it is pointless: anything other than 408, 425, 429 or a 5xx is taken as a deliberate rejection. There is still no replay endpoint, so an endpoint down for longer than that window has a gap, and the delivery log is where you find it.
- A bounced message still reads as `sent` through `GET /emails`: the delivery report is matched to the original and labelled on the thread, but nothing writes back to the send row, whose status has no bounced state. The suppression it feeds is real: a hard bounce or a complaint puts the address on this workspace’s suppression list and the next send to it is refused. It is the send record that does not learn.
- No general request rate limiter. Two counted ceilings do exist and both answer 429: a workspace that spends the monthly send allowance its plan includes gets `send_quota_exceeded` on every further send until the first of the month, and minting disposable inboxes is capped at six an hour and thirty a day per client with `too_many_inboxes`. Neither carries a `Retry-After`. A limiter on the rate of ordinary reads and writes is an absence rather than a promise, and one that will be corrected.
- No attachment UPLOAD endpoint on the API. Inline attachments are base64 and capped at 5 MB across the message. A larger file is sent as `{ fileId }`, naming a file already in the workspace, and travels as a download link. Reading attachments off received mail does work.