---
title: "Check why mail is or isn't arriving"
method: GET
path: "/v1/addresses/{address}/delivery"
---

# Check why mail is or isn't arriving

`GET /v1/addresses/{address}/delivery`

## Request

- Base URL: `https://api.proxymail.qa`
- URL: `https://api.proxymail.qa/v1/addresses/{address}/delivery`
- Auth: HTTP bearer

What has reached the address, every message we refused for it (too large, or over an hourly or daily limit) and one sentence on what that means, such as an email provider in sandbox mode. Doesn't wait. A 404 says what an unknown address can mean.

## Path parameters

- `address` string, email, required

## Response `200`

The address's delivery status

- object
  - `address` string
  - `created_at` string, date-time
  - `expires_at` string, date-time
  - `receiving` boolean: False once the address has expired: mail to it is refused.
  - `emails` integer: Emails received so far.
  - `last_email_at` string, date-time, nullable
  - `refused` object[]: Mail we refused for the address, newest first. Refusals for the same reason within an hour share one entry with a count.
    - `reason` 'too_large' | 'address_limit' | 'daily_limit'
    - `first_at` string, date-time
    - `last_at` string, date-time
    - `count` integer
    - `size_bytes` integer, nullable: The largest refused message, in bytes.
  - `hint` string: What the status means, most important first.
  - `help` string, uri

## Other responses

- `404`: Nothing arrived in time, or the address isn't in this project. hint says why as far as we can tell; after a wait, refused lists mail we turned away since `since`.

---

[API](https://skmtc.dev/proxymail/apis/proxy-mail-qa-api.md) · [All operations](https://skmtc.dev/proxymail/apis/proxy-mail-qa-api/llms.txt) · [OpenAPI document](https://skmtc.dev/proxymail/apis/proxy-mail-qa-api/revisions/8f8a5e84cf5c?raw)
