---
title: "Entra Assurance Resend"
method: POST
path: "/v1/auth/entra/email-assurance/resend"
tags: ["auth"]
---

# Entra Assurance Resend

`POST /v1/auth/entra/email-assurance/resend`

## Request

- Base URL: `https://api.patricia.app` (the document declares no server; this is the origin it was published from)
- URL: `https://api.patricia.app/v1/auth/entra/email-assurance/resend`
- Auth: none declared

Mail another link for a ceremony still waiting on its mailbox.

The same per-minute limit as its siblings, which is deliberately not where this route is
bounded: it is the one that SENDS, so its real ceilings are durable and live in the service —
the challenge's own send budget, the cooldown between messages, and the per-address and
per-principal windows. The edge limit only stops a caller reaching those as fast as the
network allows.

## Request body

- EntraAssuranceResumeRequest: The ceremony secret; resume also reads the optional first-time answer.
  - `resume_token` string, required
  - `first_time` boolean

## Response `200`

Successful Response

- EntraAssuranceStatusResponse: What the waiting page renders. Carries no secret and nothing about any account.
  - `status` string, required
  - `expires_at` string, date-time, required
  - `support_ref` string, required
  - `resend_available` boolean, required

## Other responses

- `422`: Validation Error

---

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