# Redirect to Harness Artifact Page

Redirect to Harness Artifact Page

Endpoint: GET /har/api/v1/registry/{registry_identifier}/artifact/{artifact}/redirect
Version: 1.0
Security: x-api-key

## Path parameters:

  - `registry_identifier` (string, required)
    Unique registry Identifier in a account.

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

## Query parameters:

  - `accountIdentifier` (string)
    Account Identifier

  - `version` (string)
    Version

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


## Response 302 fields