---
title: "Resend an email recipient's confirmation message (issue"
method: POST
path: "/api/v1/recipients/{recipientID}/confirm/resend"
---

# Resend an email recipient's confirmation message (issue

`POST /api/v1/recipients/{recipientID}/confirm/resend`

## Request

- Base URL: `https://api.uptimemonitoring.com`
- URL: `https://api.uptimemonitoring.com/api/v1/recipients/{recipientID}/confirm/resend`
- Auth: HTTP bearer

`type=email` only. Two-phase: stages a new confirmation token,
sends it, then activates on success — a transient send failure
never invalidates a previously-mailed link still in the
recipient's inbox. Rate-limited to 5 per address per hour,
process-wide across accounts.

## Response `202`

Confirmation resent

## Other responses

- `404`: Recipient not found
- `409`: Recipient is already confirmed, OR the mail was sent but the token it carries is no longer live (a concurrent resend or address change superseded it, or the recipient was deleted, between sending and activation) — the caller should retry the resend.
- `429`: Resent too recently (60s cooldown), or rate-limited
- `503`: Sending the confirmation message failed

---

[API](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api.md) · [All operations](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api/llms.txt) · [OpenAPI document](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api/revisions/ddcb2a8bc70f?raw)