curl -X POST "https://api.scanova.io/multi-users/118/resend-invitation/" \
-H "Authorization: YOUR_API_KEY"
"Invitation resent"
Shared Users & Roles
Resend a shared-user's invitation email
POST /multi-users//resend-invitation/
POST
/
multi-users
/
{pk}
/
resend-invitation
/
curl -X POST "https://api.scanova.io/multi-users/118/resend-invitation/" \
-H "Authorization: YOUR_API_KEY"
"Invitation resent"
Resends the invitation email for a shared user who hasn’t accepted yet, on
Resending refreshes
api.scanova.io, authenticated with your raw API key.
POST https://api.scanova.io/multi-users/{pk}/resend-invitation/
Authorization: YOUR_API_KEY
integer
required
The shared user’s
id, from List shared users.curl -X POST "https://api.scanova.io/multi-users/118/resend-invitation/" \
-H "Authorization: YOUR_API_KEY"
"Invitation resent"
invitation_sent_on, which extends the invitation link’s validity window — a teammate whose original invite expired can still accept after a resend. 404 if pk isn’t a shared user on this account (including one who already accepted — there’s nothing to resend at that point, since Accept a shared-user invitation invalidates the hash on use).
Related
- Invite a shared user — the original invitation this resends.
- List shared users — check
is_invitation_acceptedbefore resending. - Accept a shared-user invitation — what the teammate does with the resent link.
- API overview — the auth scheme and quota rules that apply to this endpoint.
Authorizations
Send your Management API key as the raw value of the Authorization header — no "Bearer " or "Token " prefix, and no other characters. Example: Authorization: YOUR_API_KEY. A header containing more than one space-separated part is rejected outright. Requests also require the request's Host header to be the management API host (e.g. api.scanova.io) — the same key sent to the regular API host will not authenticate.
Path Parameters
Response
"Invitation resent"
Was this page helpful?