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

# List current recipient invitation inbox

> Read pending metadata addressed to the current independently verified Auth email. Firebase recipients need no app profile/team; user-scoped MCP credentials must retain current source custody. Ordinary unverified email is allowed. No email/team override, token, approval proof, automatic join or profile provisioning. IDs are hints, not resource authority. Cursor binds current recipient UID, email, incarnation and pending status; empty filtered pages may still have more. Admin acceptance separately requires verified email and owner approval.



## OpenAPI

````yaml openapi.json GET /teams/invitations/inbox
openapi: 3.0.3
info:
  title: gigstack API v2
  description: >
    # gigstack API v2


    Build customer, invoice and payment integrations. Start with the
    [quickstart](https://docs.gigstack.io/quickstart), then select the [issuing
    country](https://docs.gigstack.io/concepts/shared-fields).


    ## Authentication and environments


    Use Authorization: Bearer YOUR_API_KEY. Standard live and test keys use
    https://api.gigstack.io/v2. Internal staging uses
    https://gigstack-staging-9z9nnaat.uc.gateway.dev/v2 and separate keys. Test
    mode is a data mode within an environment; a body field does not switch a
    key's mode.


    See [authentication](https://docs.gigstack.io/authentication) for key
    handling, OAuth team scope and gigstack Connect. Internal partner
    provisioning is outside this public contract; health probes have their own
    security declarations. Operations marked unavailable have no configured
    public gateway route.


    ## Read the operation contract


    Response envelopes, pagination and retry rules differ by endpoint. HTTP
    success alone does not prove external fiscal completion or movement of
    money. Reconcile ambiguous writes before retrying. Use [responses and
    recovery](https://docs.gigstack.io/responses) and the operation's error
    codes; document credits and daily limits are not generic retryable rate
    limits.


    The issuing team's configuration selects Mexico or Colombia; customer
    country and currency do not. Read
    [Mexico](https://docs.gigstack.io/countries/mexico) or
    [Colombia](https://docs.gigstack.io/countries/colombia) before choosing
    fiscal fields. Accepted public input differs from a provider's direct
    payload.


    Examples and schema checks do not imply every operation has been executed
    live. [Verification coverage](https://docs.gigstack.io/verification)
    distinguishes source review, offline checks and observed staging behavior.
    Documentation describes operations and does not authorize execution.
  version: 2.0.0
  contact:
    name: Gigstack API Support
    url: https://gigstack.io
    email: support@gigstack.io
  license:
    name: Proprietary
    url: https://gigstack.io/terms
  termsOfService: https://gigstack.io/terms
servers:
  - url: https://api.gigstack.io/v2
    description: >
      Public API for standard live and test-mode keys. Test data is isolated by
      the key mode

      (`livemode: false`). Internal staging is a separate deployment and key
      store; see

      https://docs.gigstack.io/authentication#environments for its base URL.
security:
  - bearerAuth: []
externalDocs:
  description: Complete API Documentation & Guides
  url: https://docs.gigstack.io
paths:
  /teams/invitations/inbox:
    get:
      tags:
        - Teams
      summary: List current recipient invitation inbox
      description: >-
        Read pending metadata addressed to the current independently verified
        Auth email. Firebase recipients need no app profile/team; user-scoped
        MCP credentials must retain current source custody. Ordinary unverified
        email is allowed. No email/team override, token, approval proof,
        automatic join or profile provisioning. IDs are hints, not resource
        authority. Cursor binds current recipient UID, email, incarnation and
        pending status; empty filtered pages may still have more. Admin
        acceptance separately requires verified email and owner approval.
      operationId: listRecipientInvitations
      parameters:
        - name: limit
          in: query
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 25
        - name: cursor
          in: query
          schema:
            type: string
            maxLength: 1024
      responses:
        '200':
          description: Safe recipient metadata page
          content:
            application/json:
              schema:
                type: object
                additionalProperties: false
                required:
                  - success
                  - data
                  - has_more
                  - next_cursor
                properties:
                  success:
                    type: boolean
                    enum:
                      - true
                  data:
                    type: array
                    items:
                      type: object
                      additionalProperties: false
                      required:
                        - id
                        - email
                        - emailOwner
                        - rol
                        - status
                        - accepted
                        - type
                        - expiring
                        - timestamp
                        - teamId
                        - teamName
                        - billingId
                        - billingName
                        - approval_required
                        - team
                      properties:
                        id:
                          type: string
                          pattern: ^[A-Za-z0-9_-]{1,128}$
                        email:
                          type: string
                        emailOwner:
                          type: string
                          nullable: true
                        rol:
                          type: string
                          enum:
                            - admin
                            - editor
                            - viewer
                        status:
                          type: string
                          enum:
                            - pending
                        accepted:
                          type: boolean
                          enum:
                            - false
                        type:
                          type: string
                          enum:
                            - team
                            - billingAccount
                        expiring:
                          type: number
                        timestamp:
                          type: number
                          nullable: true
                        teamId:
                          type: string
                          pattern: ^[A-Za-z0-9_-]{1,128}$
                          nullable: true
                        teamName:
                          type: string
                          nullable: true
                        billingId:
                          type: string
                          pattern: ^[A-Za-z0-9_-]{1,128}$
                        billingName:
                          type: string
                          nullable: true
                        approval_required:
                          type: boolean
                        team:
                          type: object
                          nullable: true
                          additionalProperties: false
                          required:
                            - id
                            - alias
                            - logo
                            - primaryColor
                            - billingAccount
                            - members
                          properties:
                            id:
                              type: string
                              pattern: ^[A-Za-z0-9_-]{1,128}$
                            alias:
                              type: string
                              nullable: true
                            logo:
                              type: string
                              nullable: true
                            primaryColor:
                              type: string
                              nullable: true
                            billingAccount:
                              type: string
                              pattern: ^[A-Za-z0-9_-]{1,128}$
                            members:
                              type: integer
                              minimum: 0
                  has_more:
                    type: boolean
                  next_cursor:
                    type: string
                    nullable: true
                    maxLength: 1024
        '400':
          description: Invalid query/cursor
        '401':
          description: Invalid or revoked original user credential
        '403':
          description: Inactive profile or credential scope
        '503':
          description: Read unavailable; never interpret as empty inbox
      security:
        - bearerAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >
        **Authentication Method:** HTTP Bearer token.


        The runtime requires the literal `Bearer ` prefix — a bare token in the

        `Authorization` header is rejected with `401 unauthorized`.


        **Header Format:** `Authorization: Bearer YOUR_API_KEY`


        Your API key is a JWT. Live keys operate on live data (`livemode:
        true`);

        test keys operate on isolated test data (`livemode: false`).


        **Get your key at:**
        [app.gigstack.pro/settings?tab=api](https://app.gigstack.pro/settings?tab=api)


        **Errors:** credential failures are answered by the authentication layer
        with a raw

        `{ "message": … }` body, not the standardized envelope — `401` for a
        missing, malformed or

        expired token, `403` for a revoked key or a plan without API access. See
        the `Unauthorized`

        and `AuthForbidden` responses.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.