# Create a bulk download request

Create a bulk download request

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

## Response 200 fields (application/json):

  - `data` (object, required)

  - `data.downloadId` (string, required)
    Unique identifier for the download request
    Example: "12345678-1234-1234-1234-123456789012"

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

## Response 401 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 403 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 404 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 500 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"