> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Resend a shared-user's invitation email

> POST /multi-users/{pk}/resend-invitation/

Resends the invitation email for a shared user who hasn't accepted yet, on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key.

```
POST https://api.scanova.io/multi-users/{pk}/resend-invitation/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<ParamField path="pk" type="integer" required>
  The shared user's `id`, from [List shared users](/api-reference/management-api/shared-users/list).
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://api.scanova.io/multi-users/118/resend-invitation/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  "Invitation resent"
  ```
</ResponseExample>

Resending refreshes `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](/api-reference/management-api/shared-users/accept-invitation) invalidates the hash on use).

## Related

* [Invite a shared user](/api-reference/management-api/shared-users/invite) — the original invitation this resends.
* [List shared users](/api-reference/management-api/shared-users/list) — check `is_invitation_accepted` before resending.
* [Accept a shared-user invitation](/api-reference/management-api/shared-users/accept-invitation) — what the teammate does with the resent link.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota rules that apply to this endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json POST /multi-users/{pk}/resend-invitation/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    api.scanova.io (QR codes, folders, tags, leads, forms, analytics, plans,
    shared users & roles), plus the token-creation and usage-stats endpoints
    used to authenticate against it. Every path and request/response shape below
    was verified live against a real API key and the actual running backend
    (Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
  version: 2.0.0
servers:
  - url: https://api.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /multi-users/{pk}/resend-invitation/:
    post:
      summary: Resend a shared-user's invitation email
      description: >-
        Resending refreshes `invitation_sent_on`, which extends the invitation
        link's validity window (INVITATION_LINK_VALIDITY_DAYS from the most
        recent send).
      operationId: resendManagedInvitation
      parameters:
        - name: pk
          in: path
          required: true
          schema:
            type: integer
      responses:
        '200':
          description: '"Invitation resent"'
        '404':
          description: No shared user with this id owned by this account.
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Send your Management API key as the raw value of the Authorization
        header — no "Bearer " or "Token " prefix, and no other characters.
        Example: `Authorization: 401f7ac837da42b97f613d789819ff93537bee6a`. 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.

````