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

# List push token metadata

> Requires connectors:admin on the instance's Organization and Corpus. Returns metadata only, including expired or revoked tokens, never secrets or hashes. Pages are ordered by token_id; next_after is the next page's after value. Disabled instances remain readable.



## OpenAPI

````yaml /openapi.yaml get /v0/connectors/{connector_id}/tokens
openapi: 3.1.0
info:
  title: Quivr HTTP API
  version: 0.0.0-draft
  description: >-
    Every endpoint of the Quivr v0 HTTP API. Send an API key as a bearer token;
    the key decides the Organization, the actions and the Corpora a request may
    reach.
servers: []
security:
  - ApiKey: []
paths:
  /v0/connectors/{connector_id}/tokens:
    parameters:
      - name: connector_id
        in: path
        required: true
        schema:
          type: string
          minLength: 1
    get:
      tags:
        - Connectors
      summary: List push token metadata
      description: >-
        Requires connectors:admin on the instance's Organization and Corpus.
        Returns metadata only, including expired or revoked tokens, never
        secrets or hashes. Pages are ordered by token_id; next_after is the next
        page's after value. Disabled instances remain readable.
      operationId: listConnectorTokens
      parameters:
        - name: after
          in: query
          schema:
            type: string
            maxLength: 128
        - name: limit
          in: query
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 100
      responses:
        '200':
          description: Token metadata page.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ConnectorTokenList'
        default:
          description: >-
            JSON Error envelope; 401 unauthenticated, 403 without admin
            permission, 404 out of scope, 422 invalid pagination, 503
            unavailable.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    ConnectorTokenList:
      type: object
      additionalProperties: false
      required:
        - items
      properties:
        items:
          type: array
          items:
            $ref: '#/components/schemas/ConnectorToken'
        next_after:
          type: string
    Error:
      type: object
      additionalProperties: false
      properties:
        code:
          type: string
          minLength: 1
        message:
          type: string
          minLength: 1
        retryable:
          type: boolean
        field:
          type: string
          minLength: 1
          description: >-
            JSON Pointer (RFC 6901) to the request member that caused a 422,
            when known (for example /config/url or /credential/secret/token on
            connector commands).
        resync_url:
          type: string
          format: uri-reference
      required:
        - code
        - message
        - retryable
    ConnectorToken:
      type: object
      additionalProperties: false
      required:
        - token_id
        - prefix
        - created_at
      properties:
        token_id:
          type: string
        prefix:
          type: string
          description: Display prefix only; cannot authenticate.
        created_at:
          type: string
          format: date-time
        rotated_at:
          type: string
          format: date-time
        revoked_at:
          type: string
          format: date-time
        valid_until:
          type: string
          format: date-time
          description: >-
            Exclusive expiry of an old token after rotation; absent for an
            unrotated token.
  securitySchemes:
    ApiKey:
      type: http
      scheme: bearer
      description: >-
        API key, not necessarily a JWT. Server derives Organization, permitted
        actions and Corpus scope; every resource access is authorized.

````

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