---
title: "Resend a user invitation"
method: POST
path: "/v2/users/{user_id}/resend-invitation"
tags: ["Users"]
---

# Resend a user invitation

`POST /v2/users/{user_id}/resend-invitation`

Resend the invitation email for a pending (unverified) user. Generates a
new verification token and sends a fresh email to the user's address.

The target user must be in the `INVITED` state (unverified and active).
Returns 400 if the user has already verified their account, or if
SAML/IdP login is enforced for the account.

This is a fire-and-forget operation: a 204 response means the token was
regenerated and the email dispatch was accepted. If the email fails to send,
the endpoint still returns 204 and logs the error internally.

Requires account admin role or USER_CREATE permission.

<Note>This endpoint is in beta, read more [here](https://arize.com/docs/ax/rest-reference#api-version-stages).</Note>

## Path parameters

- `user_id` string, required — A universally unique identifier (base64-encoded opaque string).

## Response `204`

Invitation resend accepted (no content)

## Other responses

- `400` — Invalid request
- `401` — Authentication is required
- `403` — Insufficient permissions to access this resource
- `404` — Not found
- `429` — Rate limit exceeded

---

[API](https://skmtc.net/arize-ai/apis/arize-rest-api.md) · [All operations](https://skmtc.net/arize-ai/apis/arize-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/arize-ai/arize-rest-api/versions/2ce448f1de13/schema)