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

# Get Template by Hash

> Returns the template matching the given hash_id along with the user's saved templates, popular templates, recommended templates, and autoscaler templates.



## OpenAPI

````yaml /api-reference/openapi.yaml get /api/v0/users/{user_id}/templates/{hash_id}/
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/users/{user_id}/templates/{hash_id}/:
    get:
      tags:
        - Accounts
      summary: Get Template by Hash
      description: >-
        Returns the template matching the given hash_id along with the user's
        saved templates, popular templates, recommended templates, and
        autoscaler templates.
      parameters:
        - name: user_id
          in: path
          required: true
          schema:
            type: integer
          description: ID of the requesting user (URL path parameter)
        - name: hash_id
          in: path
          required: true
          schema:
            type: string
          description: >-
            MD5 hash identifying the specific template to look up as a referral
            or direct link
      responses:
        '200':
          description: >-
            Returns {success: true, templates, referral_templates, popular,
            recommended, autoscaler}
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    description: Always true
                  templates:
                    type: array
                    items:
                      type: object
                    description: Merged list of hashed and user templates
                  referral_templates:
                    type: array
                    items:
                      type: object
                    description: Templates matching the given hash_id
                  popular:
                    type: array
                    items:
                      type: object
                    description: Popular templates
                  recommended:
                    type: array
                    items:
                      type: object
                    description: Recommended templates
                  autoscaler:
                    type: array
                    items:
                      type: object
                    description: Autoscaler-enabled templates
      security:
        - BearerAuth: []
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: API key must be provided in the Authorization header

````