Resend a user invitation

curl --request POST \
  --url https://api.arize.com/v2/users/{user_id}/resend-invitation \
  --header 'Authorization: Bearer <token>'

{
  "status": 400,
  "title": "Invalid request parameters",
  "detail": "The 'name' field is required and must be a non-empty string.",
  "instance": "/resource",
  "type": "https://arize.com/docs/ax/rest-reference/errors#invalid-request"
}

Users

Resend a user 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.

This endpoint is in beta, read more here.

POST

users

{user_id}

resend-invitation

Resend a user invitation

curl --request POST \
  --url https://api.arize.com/v2/users/{user_id}/resend-invitation \
  --header 'Authorization: Bearer <token>'

{
  "status": 400,
  "title": "Invalid request parameters",
  "detail": "The 'name' field is required and must be a non-empty string.",
  "instance": "/resource",
  "type": "https://arize.com/docs/ax/rest-reference/errors#invalid-request"
}

Authorizations

Authorization

string

header

required

Most Arize AI endpoints require authentication. For those endpoints that require authentication, include your API key in the request header using the format

Path Parameters

user_id

string

required

The unique user identifier (base64) A universally unique identifier (base64-encoded opaque string).

Example:

"RW50aXR5OjEyMzQ1"

Response

Invitation resend accepted (no content)

Update a user Trigger a password-reset email for a user

⌘I