# Describe Docker Artifact Manifests

Get Docker Artifact Manifests

Endpoint: GET /har/api/v1/registry/{registry_ref}/artifact/{artifact}/version/{version}/docker/manifests
Version: 1.0
Security: x-api-key

## Path parameters:

  - `registry_ref` (string, required)
    Reference to the scope in which the registry exists.

Format depends on the scope:

- : 
- : 
- : 

The  suffix is used internally to route scoped requests.
It must be included  in the URL.

  - `artifact` (string, required)
    Name of the artifact.

The value depends on whether the name contains a slash ():

- If the artifact name , append a trailing  at the end.
  - Example: 
- If the artifact name , use the plain name.
  - Example: 

This is used internally to distinguish between namespaced and flat artifact names.

  - `version` (string, required)
    Name of Artifact Version.

## Response 200 fields (application/json):

  - `data` (object, required)
    Harness Manifests

  - `data.imageName` (string, required)

  - `data.manifests` (array)

  - `data.manifests.createdAt` (string)

  - `data.manifests.digest` (string, required)

  - `data.manifests.downloadsCount` (integer)

  - `data.manifests.isQuarantined` (boolean)

  - `data.manifests.osArch` (string, required)

  - `data.manifests.quarantineReason` (string)

  - `data.manifests.size` (string)

  - `data.manifests.stoDetails` (object)

  - `data.manifests.stoDetails.critical` (integer)

  - `data.manifests.stoDetails.executionId` (string)

  - `data.manifests.stoDetails.high` (integer)

  - `data.manifests.stoDetails.ignored` (integer)

  - `data.manifests.stoDetails.info` (integer)

  - `data.manifests.stoDetails.lastScanned` (string)

  - `data.manifests.stoDetails.low` (integer)

  - `data.manifests.stoDetails.medium` (integer)

  - `data.manifests.stoDetails.pipelineId` (string)

  - `data.manifests.stoDetails.total` (integer)

  - `data.manifests.stoExecutionId` (string)

  - `data.manifests.stoPipelineId` (string)

  - `data.version` (string, required)

  - `status` (string, required)
    Indicates if the request was successful or not
    Enum: "SUCCESS", "FAILURE", "ERROR"

## Response 400 fields (application/json):

  - `code` (string, required)
    The http error code
    Example: "404"

  - `details` (object)
    Additional details about the error

  - `message` (string, required)
    The reason the request failed

## Response 401 fields (application/json):

  - `code` (string, required)
    The http error code
    Example: "404"

  - `details` (object)
    Additional details about the error

  - `message` (string, required)
    The reason the request failed

## Response 403 fields (application/json):

  - `code` (string, required)
    The http error code
    Example: "404"

  - `details` (object)
    Additional details about the error

  - `message` (string, required)
    The reason the request failed

## Response 404 fields (application/json):

  - `code` (string, required)
    The http error code
    Example: "404"

  - `details` (object)
    Additional details about the error

  - `message` (string, required)
    The reason the request failed

## Response 500 fields (application/json):

  - `code` (string, required)
    The http error code
    Example: "404"

  - `details` (object)
    Additional details about the error

  - `message` (string, required)
    The reason the request failed