resend-invite

dci resend-invite <id> [body] [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.

• id — ID of the invited user — the id of a dci list-users row whose status is invited, also returned as user.id by dci invite-user.

Pass the request body as name: value arguments or pipe JSON on stdin — see Command structure.

Dry run is server-side

resend-invite carries the API's own dryRun parameter, so --dry-run sends a simulation request and returns the real response shape marked as a dry run. An --idempotency-key is required on every real call (UUID v4 or ULID recommended); when you omit it under --dry-run the CLI generates a throwaway key for you.

Examples

# Send a fresh invitation email and reset the expiry to 48 hours from now.
dci resend-invite <invite-id> --idempotency-key "$(uuidgen)"

Old email links stop working; a `Cancelled` invite is reactivated to `Pending`. Retrying with the same key returns the cached result instead of sending again.

# Simulate the resend server-side without sending anything.
dci resend-invite <invite-id> --dry-run

# Same, as JSON for scripts.
dci resend-invite <invite-id> --idempotency-key <request-key> --output json

Request

Content-Type: application/json

Raw JSON schema

{
  "type": "object"
}

Flags

Flag	Type	Default	Example	Description
--dry-run	boolean	false		If true, validates and simulates the operation without committing changes. The response shape is identical to a real execution.

Every command also accepts the CLI-wide flags for output shaping — see Output formats and Table output options.

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 to exit code mapping

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.

Related

• cancel-invite — Cancel invite
• invite-user — Invite user
• list-users — List users
• API reference: POST /iam/v1/users/{id}/actions/resend

Aliases: resendinvite