# Returns Registry Details

Returns Registry Details in the account for the given key

Endpoint: GET /har/api/v1/registry/{registry_ref}
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.

## Response 200 fields (application/json):

  - `data` (object, required)
    Harness Artifact Registry

  - `data.allowedPattern` (array)

  - `data.blockedPattern` (array)

  - `data.cleanupPolicy` (array)

  - `data.cleanupPolicy.expireDays` (integer)

  - `data.cleanupPolicy.name` (string)

  - `data.cleanupPolicy.packagePrefix` (array)

  - `data.cleanupPolicy.versionPrefix` (array)

  - `data.config` (object)
    SubConfig specific for Virtual or Upstream Registry

  - `data.config.type` (string, required)
    refers to type of registry i.e virtual or upstream
    Enum: "VIRTUAL", "UPSTREAM"

  - `data.createdAt` (string)

  - `data.deletedAt` (string)
    Timestamp in milliseconds when the artifact was soft deleted. Null if not deleted.

  - `data.description` (string)

  - `data.identifier` (string, required)

  - `data.isPublic` (boolean, required)

  - `data.labels` (array)

  - `data.modifiedAt` (string)

  - `data.packageType` (string, required)
    refers to package
    Enum: "DOCKER", "MAVEN", "PYTHON", "GENERIC", "HELM", "NUGET", "NPM", "RPM", "CARGO", "COMPOSER", "GO", "HUGGINGFACE", "CONDA", "DART", "SWIFT", "RAW"

  - `data.policyRefs` (array)

  - `data.scanners` (array)

  - `data.scanners.name` (string)
    Enum: "AQUA_TRIVY", "GRYPE"

  - `data.url` (string, required)

  - `data.uuid` (string, required)

  - `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"