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

# Regenerate Subaccount Keys

> Regenerate API keys for one specific subaccount or all subaccounts owned by the authenticated user.



## OpenAPI

````yaml /api-reference/openapi.yaml put /api/v0/subaccounts/regenerate_keys/
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
servers:
  - url: https://console.vast.ai
    description: Production server
security:
  - BearerAuth: []
paths:
  /api/v0/subaccounts/regenerate_keys/:
    put:
      tags:
        - Accounts
      summary: Regenerate Subaccount Keys
      description: >-
        Regenerate API keys for one specific subaccount or all subaccounts owned
        by the authenticated user.
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                subaccount_user_id:
                  type: integer
                  description: >-
                    ID of the specific subaccount whose key should be
                    regenerated; mutually exclusive with regenerate_all
                  example: 56789
                regenerate_all:
                  type: boolean
                  description: >-
                    If true, regenerate keys for all subaccounts by rotating the
                    owner seed; mutually exclusive with subaccount_user_id
      responses:
        '200':
          description: >-
            Keys regenerated: {"success": true, "regenerated_keys": [{"user_id":
            ..., "email": ..., "derived_key": ...}]}
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    description: Always true on success
                  regenerated_keys:
                    type: array
                    description: One entry per regenerated subaccount
                    items:
                      type: object
                      properties:
                        user_id:
                          type: integer
                          description: Subaccount user ID
                        email:
                          type: string
                          description: Subaccount email
                        derived_key:
                          type: string
                          description: New derived API key value
              example:
                success: true
                regenerated_keys:
                  - user_id: 456
                    email: sub@example.com
                    derived_key: abc123...
        '400':
          description: >-
            Invalid params: "Must specify subaccount_user_id or regenerate_all"
            or "subaccount_user_id must be a valid integer"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: >-
            Account not subaccount-approved: "Only subaccount approved accounts
            may use this API"
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: >-
            Subaccount not found: "Subaccount not found" or "Active subaccount
            key not found to regenerate"
          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

````