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

# Resend an invitation

> Rotates the token (the previous link dies) and re-enqueues the e-mail. It bypasses the seat cap on purpose: the invitation's seat is already counted, and charging again would make resend fail exactly in the full workspace, which is where it is most used.

This is what makes `sendEmail: false` recoverable — since only the hash is stored, without this route a caller who lost the response would have no way back.

**OAuth required.** A classic key (`x-api-key`) is refused: an `x-api-key` request has no user behind it, and allowing writes to the member list would turn any key of the workspace into a path to account takeover.



## OpenAPI

````yaml openapi.json POST /v1/workspace/members/{id}/resend
openapi: 3.1.0
info:
  title: Pilot Status API
  version: 1.0.0
  license:
    name: Pilot Status Terms of Service
    url: https://pilotstatus.com.br/terms
  description: >-
    Public REST API for Pilot Status. Authenticate with the `x-api-key: ps_...`
    header (or `x-api-key-id`). Base URL: https://pilotstatus.com.br
servers:
  - url: https://pilotstatus.com.br
security:
  - apiKey: []
  - apiKeyId: []
paths:
  /v1/workspace/members/{id}/resend:
    post:
      tags:
        - Workspace
      summary: Resend an invitation
      description: >-
        Rotates the token (the previous link dies) and re-enqueues the e-mail.
        It bypasses the seat cap on purpose: the invitation's seat is already
        counted, and charging again would make resend fail exactly in the full
        workspace, which is where it is most used.


        This is what makes `sendEmail: false` recoverable — since only the hash
        is stored, without this route a caller who lost the response would have
        no way back.


        **OAuth required.** A classic key (`x-api-key`) is refused: an
        `x-api-key` request has no user behind it, and allowing writes to the
        member list would turn any key of the workspace into a path to account
        takeover.
      operationId: post_workspace-member-resend
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
          description: Membership id (the `id` the list returns), NOT the user id.
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                sendEmail:
                  type: boolean
                  example: true
      responses:
        '200':
          description: Invitation resent
        '403':
          description: Insufficient role, wrong credential, or invitations disabled.
        '409':
          description: '`ALREADY_MEMBER` (already accepted) or `NOT_FOUND`.'
components:
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key
      description: Your ps_ API key
    apiKeyId:
      type: apiKey
      in: header
      name: x-api-key-id
      description: API key id (alternative to x-api-key)

````