Skip to main content
POST
/
api
/
adm
/
invitations
/
{id}
/
resend
Resend User Invitation
curl --request POST \
  --url https://localhost:44371/api/adm/invitations/{id}/resend \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{}'
{
  "success": true,
  "code": 200,
  "errorMessage": null
}

​
Description

Sends a new invitation email for an existing invitation record, using the same registration link. This is useful when the original email was not received, was deleted, or the invitation has expired and needs to be renewed with a new expiration date.

​
Input

  • Path Parameter: id (guid, required) — Unique identifier of the invitation to resend.
  • Body: model (UserInvitationResendCommandRequest, required) — Resend options including:
    • extendExpiration (bool, optional) — Whether to extend the expiration date.
    • message (string, optional) — Optional updated personalized message.

​
Output

Returns a UserInvitationResendCommandResponse indicating whether the email was resent successfully.

​
Example Request

POST /api/admin/userInvitations/9ef15c43-a955-6f4h-c7g3-1h6d4f0e3g9c/resend
Content-Type: application/json
Authorization: Bearer {token}

{
  "extendExpiration": true,
  "message": "Reminder: Please complete your registration"
}

​
Example Response

{
  "success": true,
  "code": 200,
  "errorMessage": null
}

​
Errors

  • 400 Bad Request — Invitation already accepted or invitation cancelled.
  • 404 Not Found — No invitation exists with the specified ID.

​
Notes

  • Resending typically extends the expiration date if configured to do so.
  • The same registration link is used; a new invitation is not created.
  • Accepted invitations cannot be resent.
  • Failed email sends are logged but don’t prevent the operation from succeeding.

Authorizations

​
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Path Parameters

​
id
string<guid>
required

The unique identifier of the invitation to resend.

Body

application/json

The resend request containing optional updated message or settings.

Base structure for command requests that modify data. Represents the command to resend a previously issued invitation.

​
joinLink
string | null

The link that recipients can use to rejoin the platform.

Response

Always returned. Check the success property in the response body to determine if the operation succeeded.

Standard response structure containing operation status and error information. Standard command response indicating the result of a data modification. Represents the response returned after resending an invitation.

​
success
boolean

True if the operation completed successfully; false if an error occurred.

Example:

true

​
code
enum<string>

Result code indicating the outcome of the operation.

Available options:
Unknown,
Success,
BadRequest,
Unauthorized,
NotFound,
Error
Example:

200

​
errorMessage
string | null

Human-readable error message when an error occurs.

Example:

null