---
title: "Send a new \"Confirm your email\" link to the signed-in user's own address. The answer is always 202"
method: POST
path: "/v1/auth/email-confirm/request"
---

# Send a new "Confirm your email" link to the signed-in user's own address. The answer is always 202

`POST /v1/auth/email-confirm/request`

## Request

- Base URL: `https://api.evictionsapi.com`
- URL: `https://api.evictionsapi.com/v1/auth/email-confirm/request`
- Auth: HTTP bearer

## Response `202`

The request was accepted. If the address is not confirmed yet, a single-use link valid for three days was emailed to it. One account is sent at most 3 such emails an hour, the one at sign-up included: a request beyond that gets this same answer and sends nothing. An `Idempotency-Key` header is ignored.

- object
  - `ok` unknown, required

## Other responses

- `400`: The request is invalid.
- `401`: No valid session.
- `403`: The credential is not allowed to do this (`forbidden`). For a signed-in session: `permission_denied`, the person's role in the organization lacks the permission this needs (ask an owner); `no_organization`, the person belongs to no organization yet (start one with `POST /v1/me/organizations` or accept an invitation).
- `404`: Not found.
- `409`: The request conflicts with the current state: for a case, it is not in a state that allows this, or its details were erased (`erased`); for an API key, a limit or the key in use.
- `413`: The request body is too large.
- `422`: The case did not pass a check.
- `429`: Too many email confirmation requests from this address: at most 10 every 10 minutes, counting both confirmation endpoints. `Retry-After` gives the seconds to wait.

---

[API](https://skmtc.dev/evictionsapi/apis/evictions-api.md) · [All operations](https://skmtc.dev/evictionsapi/apis/evictions-api/llms.txt) · [OpenAPI document](https://skmtc.dev/evictionsapi/apis/evictions-api/revisions/28459213a1a3?raw)