> ## 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 your notifications

> Requires a verified Firebase ID token or signed, active personal MCP token. Team API keys and OAuth client credentials cannot act as their creator. Firebase callers may access their own identity before joining a team. MCP callers remain subject to current credential/team authorization. Authentication is verified in the backend, including when requests pass through the API gateway.

Dismissed entries are excluded. Ordered by delivery date and recipient ID descending. Follow next_cursor until has_more is false.



## OpenAPI

````yaml openapi.json GET /users/me/notifications
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:
  /users/me/notifications:
    get:
      tags:
        - Your Account
      summary: List your notifications
      description: >-
        Requires a verified Firebase ID token or signed, active personal MCP
        token. Team API keys and OAuth client credentials cannot act as their
        creator. Firebase callers may access their own identity before joining a
        team. MCP callers remain subject to current credential/team
        authorization. Authentication is verified in the backend, including when
        requests pass through the API gateway.


        Dismissed entries are excluded. Ordered by delivery date and recipient
        ID descending. Follow next_cursor until has_more is false.
      operationId: listSelfNotifications
      parameters:
        - name: limit
          in: query
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 50
        - name: cursor
          in: query
          schema:
            type: string
          description: >-
            Opaque next_cursor returned by the previous page; bound to this
            user.
      responses:
        '200':
          description: Persisted account state or action result.
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                  data:
                    type: array
                    items:
                      $ref: '#/components/schemas/SelfNotification'
                  timestamp:
                    type: number
                  has_more:
                    type: boolean
                  next_cursor:
                    type: string
                    nullable: true
                required:
                  - success
                  - data
                  - timestamp
                  - has_more
                  - next_cursor
        '400':
          description: Invalid fields, empty patch, or invalid cursor.
        '401':
          description: A valid Firebase or personal MCP credential is required.
        '403':
          description: >-
            Disabled account, blocked membership, or insufficient account
            authority.
        '404':
          description: Resource not found within your authorized scope.
        '409':
          description: >-
            Context mismatch, changed membership, or personal token limit
            reached.
        '500':
          description: Internal failure. Reconcile current state before retrying a write.
      security:
        - bearerAuth: []
components:
  schemas:
    SelfNotification:
      type: object
      properties:
        id:
          type: string
        notification_id:
          type: string
          nullable: true
        team_id:
          type: string
          nullable: true
        delivered_at:
          type: number
          nullable: true
        read_at:
          type: number
          nullable: true
        dismissed_at:
          type: number
          nullable: true
        type:
          type: string
          nullable: true
        priority:
          type: string
          nullable: true
        title:
          type: string
          nullable: true
        body:
          type: string
          nullable: true
        cta:
          type: object
          properties:
            text:
              type: string
              nullable: true
            link:
              type: string
              nullable: true
          required:
            - text
            - link
          nullable: true
        expires_at:
          type: number
          nullable: true
      required:
        - id
        - notification_id
        - team_id
        - delivered_at
        - read_at
        - dismissed_at
        - type
        - priority
        - title
        - body
        - cta
        - expires_at
  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.