# Describe Docker Artifact Integration Detail

Get Docker Artifact Integration Details

Endpoint: GET /har/api/v1/registry/{registry_ref}/artifact/{artifact}/version/{version}/docker/integrationdetails
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:

- Account-level: account_id/registry_name/+
- Organization-level: account_id/org_id/registry_name/+
- Project-level: account_id/org_id/project_id/registry_name/+

The /+ suffix is used internally to route scoped requests.
It must be included exactly as shown in the URL.

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

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

- If the artifact name contains /, append a trailing /+ at the end.
  - Example: mygroup/myartifact/+
- If the artifact name does not contain /, use the plain name.
  - Example: myartifact

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

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

## Query parameters:

  - `digest` (string, required)
    Digest.

  - `version_type` (string)
    Version Type.
    Enum: "DIGEST", "TAG"

## Response 200 fields (application/json):

  - `data` (object, required)
    Docker Artifact Detail

  - `data.buildDetails` (object)

  - `data.buildDetails.orgIdentifier` (string)

  - `data.buildDetails.pipelineDisplayName` (string)

  - `data.buildDetails.pipelineExecutionId` (string)

  - `data.buildDetails.pipelineIdentifier` (string)

  - `data.buildDetails.projectIdentifier` (string)

  - `data.buildDetails.stageExecutionId` (string)

  - `data.buildDetails.stepExecutionId` (string)

  - `data.deploymentsDetails` (object)

  - `data.deploymentsDetails.nonProdDeployment` (integer, required)

  - `data.deploymentsDetails.prodDeployment` (integer, required)

  - `data.deploymentsDetails.totalDeployment` (integer, required)

  - `data.sbomDetails` (object)

  - `data.sbomDetails.allowListViolations` (integer)

  - `data.sbomDetails.artifactId` (string)

  - `data.sbomDetails.artifactSourceId` (string)

  - `data.sbomDetails.avgScore` (string)

  - `data.sbomDetails.componentsCount` (integer)

  - `data.sbomDetails.denyListViolations` (integer)

  - `data.sbomDetails.maxScore` (string)

  - `data.sbomDetails.orchestrationId` (string)

  - `data.sbomDetails.orgId` (string)

  - `data.sbomDetails.projectId` (string)

  - `data.slsaDetails` (object)

  - `data.slsaDetails.provenanceId` (string)

  - `data.slsaDetails.status` (string)

  - `data.stoDetails` (object)

  - `data.stoDetails.critical` (integer)

  - `data.stoDetails.executionId` (string)

  - `data.stoDetails.high` (integer)

  - `data.stoDetails.ignored` (integer)

  - `data.stoDetails.info` (integer)

  - `data.stoDetails.lastScanned` (string)

  - `data.stoDetails.low` (integer)

  - `data.stoDetails.medium` (integer)

  - `data.stoDetails.pipelineId` (string)

  - `data.stoDetails.total` (integer)

  - `status` (string, required)
    Request processing status indicator
    Enum: "SUCCESS", "FAILURE", "ERROR"

## Response 400 fields (application/json):

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

  - `details` (object)
    Additional context and details about the error.
May include field-specific validation errors or debugging information.
    Example: {"field":"registry_identifier","reason":"Registry does not exist in the specified project","value":"invalid-registry"}

  - `message` (string, required)
    Human-readable error message explaining what went wrong
    Example: "Registry not found"