> ## Documentation Index
> Fetch the complete documentation index at: https://vastai-80aa3a82-auto-openapi-preview-pr-5002.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Team API Keys

> Returns all active API keys for team members grouped by role, showing which member holds each key.



## OpenAPI

````yaml /api-reference/openapi.yaml get /api/v0/team/apikeys
openapi: 3.1.0
info:
  title: Vast.ai API
  description: >-
    Vast.ai REST API for managing GPU cloud instances, machine operations, and
    AI/ML workflows.


    ## AI Agent Quick-Start


    Install the CLI skill for your agent (Claude Code, Cursor, Windsurf, etc.):
      npx skills add vast-ai/vast-cli

    CLI reference:
    https://raw.githubusercontent.com/vast-ai/vast-cli/master/vastai/SKILL.md

    SDK reference:
    https://raw.githubusercontent.com/vast-ai/vast-cli/master/vastai_sdk/SKILL.md


    ## Auth

    All endpoints require `Authorization: Bearer $VAST_API_KEY`.

    Get your key at: https://cloud.vast.ai/manage-keys/


    ## Key Quirks

    - `gpu_ram` in CLI = GB; in REST API = MB (CLI auto-converts)

    - SSH keys must be registered BEFORE creating an instance (VM: no recovery;
    Docker: can add post-create)

    - `onstart` field is limited to 4048 characters -- gzip+base64 for longer
    scripts

    - `POST /api/v0/asks/{id}/` (create instance) returns `new_contract` as the
    instance ID, not `id`

    - Poll trap: if `actual_status` becomes `exited`, `unknown`, or `offline` it
    will never reach `running` -- destroy and retry
  version: 1.0.0
  contact:
    name: Vast.ai Support
    url: https://discord.gg/vast
  license:
    name: Vast.ai Terms of Service
    url: https://vast.ai/terms/
servers:
  - url: https://console.vast.ai
    description: Production server
security:
  - BearerAuth: []
paths:
  /api/v0/team/apikeys:
    get:
      tags:
        - Team
      summary: Get Team API Keys
      description: >-
        Returns all active API keys for team members grouped by role, showing
        which member holds each key.
      operationId: getTeamAPIKeys
      responses:
        '200':
          description: >-
            {"success": true, "keys_found": N, "keys": {<rights_id>: [{id,
            user_id, username, key, key_type, created_at, role_name}]}} or
            {"success": false, "msg": "No active team API keys found."}
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    description: True if keys were found, false if none
                  keys_found:
                    type: integer
                    description: >-
                      Total number of active keys returned (present when keys
                      exist)
                  keys:
                    type: object
                    description: Map of rights_id to array of key objects for that role
                    additionalProperties:
                      type: array
                      items:
                        type: object
                        properties:
                          id:
                            type: integer
                            description: API key record ID
                          user_id:
                            type: integer
                            description: ID of the key owner
                          username:
                            type: string
                            description: Full name or username of the key owner
                          key:
                            type: string
                            description: Key value (always empty string for security)
                          key_type:
                            type: string
                            description: 'Type of key: ''team'' or ''api'''
                          created_at:
                            type: number
                            description: Unix timestamp of key creation
                          role_name:
                            type: string
                            description: Name of the role associated with this key
                  msg:
                    type: string
                    description: Present when no keys are found
              example:
                success: true
                keys_found: 1
                keys:
                  '7':
                    - id: 200
                      user_id: 101
                      username: alice
                      key: ''
                      key_type: team
                      created_at: 1700000000
                      role_name: team_manager
        '404':
          description: >-
            "Cannot Retrieve Team Keys: User is not a team account" or "Team
            owner not found for team"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - BearerAuth: []
components:
  schemas:
    Error:
      type: object
      properties:
        error:
          type: string
        msg:
          type: string
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: API key must be provided in the Authorization header

````