resend-invite

dci resend-invite id [flags]

Resets the invite expiry to 48 hours from now, invalidates the previous invite token (so old email links stop working), and triggers a fresh invitation email. Works on invites in any state including Cancelled — resending a cancelled invite reactivates it to Pending.

Returns 404 if no invite exists for the given ID (never created, or already accepted and removed).

Requires usersManager permission.

Request

Content-Type: application/json

Schema

{
  "type": "object"
}

Flags

--dry-run: (boolean default:false)

Output

OK - Invite resent and expiry reset.

By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.

Field	Type	Description
message	string	Success message
inviteId	string	The invite document ID.

Raw JSON schema

{
  "type": "object",
  "description": "Response confirming invite resend.",
  "required": [
    "message",
    "inviteId"
  ],
  "properties": {
    "message": {
      "type": "string",
      "description": "Success message"
    },
    "inviteId": {
      "type": "string",
      "description": "The invite document ID."
    }
  }
}

Errors

On failure, dci prints a single error message — with a hint when one is available — and exits with a typed code your scripts can branch on. See Errors and exit codes for the full contract.

HTTP status	Exit code	Error code	Meaning
400	30	VALIDATION_ERROR	The arguments or request body were rejected. Review the command's flags and payload.
401	10	AUTHENTICATION_FAILED	Not signed in, or the API token is invalid. Run dci login or check DCI_API_KEY.
403	11	PERMISSION_DENIED	The DoiT user or the active customer context does not have access.
404	20	RESOURCE_NOT_FOUND	The requested resource does not exist. Check the identifier argument.
500	40	API_SERVER_ERROR	The API failed to process the request. Retryable; contact DoiT support if it persists.

Aliases: resendinvite