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

> ## Agent Instructions
> Describe what the running code does. Do not invent hosted pricing, launch dates, or security guarantees. Share and viewer links are a configured base URL plus an artifact path. Show localhost and a placeholder origin such as https://library.example.com.

# List API keys for the session

> Requires a browser session. Returns names and starting characters, not the secret. Better Auth JSON `{ apiKeys, total }`.



## OpenAPI

````yaml /api-reference/openapi.json get /api/auth/api-key/list
openapi: 3.1.0
info:
  title: Factrove HTTP API
  version: 0.1.0
  description: >-
    Generated from `@factrove/contracts` schemas and the HTTP operation catalog.
    Product routes live under `/api/v1`. Auth and API key management live under
    `/api/auth`. Do not treat this file as hand-written. Run `pnpm docs:openapi`
    after contract or route-catalog changes.
servers:
  - url: http://localhost:3001
    description: Local development API origin
  - url: https://api.example.com
    description: Example self-hosted API origin
security: []
tags:
  - name: Health
    description: Process liveness.
  - name: Auth
    description: Sessions and API keys.
  - name: Artifacts
    description: Upload, list, rename, delete, detail, and content.
  - name: Shares
    description: Owner public-link and password controls.
  - name: Public
    description: Anonymous share detail, unlock, and HTML.
paths:
  /api/auth/api-key/list:
    get:
      tags:
        - Auth
      summary: List API keys for the session
      description: >-
        Requires a browser session. Returns names and starting characters, not
        the secret. Better Auth JSON `{ apiKeys, total }`.
      operationId: listApiKeys
      responses:
        '200':
          description: Keys for the signed-in user, without `key`.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListApiKeysResponse'
              example:
                apiKeys:
                  - id: key_example
                    name: cli
                    start: ftrv_example1
                total: 1
        '401':
          description: No browser session, or Authorization was also sent.
      security:
        - sessionCookie: []
components:
  schemas:
    ListApiKeysResponse:
      type: object
      properties:
        apiKeys:
          type: array
          items:
            type: object
            properties:
              id:
                type: string
              name:
                type: string
              start:
                anyOf:
                  - type: string
                  - type: 'null'
            required:
              - id
            additionalProperties: {}
        total:
          type: integer
          minimum: 0
          maximum: 9007199254740991
      required:
        - apiKeys
        - total
      additionalProperties: {}
  securitySchemes:
    sessionCookie:
      type: apiKey
      in: cookie
      name: better-auth.session_token
      description: >-
        Better Auth session cookie from email/password sign-in. On an https API
        origin the name is `__Secure-better-auth.session_token`. On http it is
        `better-auth.session_token`. Host-only unless AUTH_COOKIE_DOMAIN is set.
        Use a cookie jar instead of typing the name.

````

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