# Get artifact stats

Get artifact stats

Endpoint: GET /har/api/v1/spaces/{space_ref}/artifact/stats
Version: 1.0
Security: x-api-key

## Path parameters:

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

Format depends on the scope:

- Account-level: account_id/+
- Organization-level: account_id/org/+
- Project-level: account_id/org/project/+

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

## Query parameters:

  - `from` (string)
    Date. Format - MM/DD/YYYY

  - `to` (string)
    Date. Format - MM/DD/YYYY

## Response 200 fields (application/json):

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

  - `data.downloadCount` (integer)

  - `data.downloadSize` (integer)

  - `data.totalStorageSize` (integer)

  - `data.uploadSize` (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"