Get Artifact

GET

/registry/v1/workspaces/{workspace}/engines/qibdo/namespaces/{namespace}/repositories/{repository}/artifacts/{reference}

curl --request GET \
  --url https://example.com/registry/v1/workspaces/example/engines/qibdo/namespaces/example/repositories/example/artifacts/example

Returns one artifact by digest or by tag name (the registry resolves both). The returned Artifact includes the full set of tags inline.

Parameters

Path Parameters

workspace

required

string

Workspace UUID — must match the authorized scope.

namespace

required

string

Parent namespace UUID.

repository

required

string

Parent repository UUID.

reference

required

string

Digest or tag identifying the artifact to retrieve.

Responses

200

OK

Media type application/json

An OCI artifact: a manifest (the JSON document the registry stores) plus the blobs it references (image layers, configs). Identified by content-derived digest. May have zero or more tags pointing at it; deleting a tag does not delete the artifact.

object

digest

Content-derived identifier (sha256:…). Stable for the lifetime of the manifest.

stringOutput only

repository_id

Parent repository UUID — identifies the repository this artifact lives in.

stringOutput only

size_bytes

Total size of the manifest plus its referenced blobs, in bytes.

stringOutput only

media_type

OCI media type (e.g. application/vnd.oci.image.manifest.v1+json).

stringOutput only

tags

All tags currently pointing at this manifest (the registry returns these inline via ?with_tag=true). Empty when the artifact is referenced only by digest.

Array<object>Output only

A mutable label that points at an artifact’s manifest digest. Multiple tags can point at the same digest; deleting a tag (DeleteTag) does not delete the underlying manifest unless it was the last reference.

object

name

The tag name as understood by docker pull foo:<name>. Unique per repository.

stringOutput only

digest

The digest of the manifest this tag currently points at.

stringOutput only

pushed_at

When this tag was last pushed (i.e. the most recent docker push image:<name>).

string format: date-time Output only

immutable

True when the repository’s immutable-tag policy applies to this tag — the registry refuses to overwrite it on push.

booleanOutput only

pushed_at

When the manifest was first pushed.

string format: date-time Output only

pulled_at

Most recent pull time, if any.

string format: date-time Output only

scan_status

Latest scan status reported by the configured scanner.

string format: enum Output only

Allowed values: ARTIFACT_SCAN_STATUS_UNSPECIFIED ARTIFACT_SCAN_STATUS_NOT_SCANNED ARTIFACT_SCAN_STATUS_SCANNING ARTIFACT_SCAN_STATUS_SCANNED ARTIFACT_SCAN_STATUS_FAILED

Example

{
  "scan_status": "ARTIFACT_SCAN_STATUS_UNSPECIFIED"
}

default

Default error response

Media type application/json

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.

object

code

The status code, which should be an enum value of [google.rpc.Code][google.rpc.Code].

integer format: int32

message

A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the [google.rpc.Status.details][google.rpc.Status.details] field, or localized by the client.

string

details

A list of messages that carry the error details. There is a common set of message types for APIs to use.

Array<object>

Contains an arbitrary serialized message along with a @type that describes the type of the serialized message.

object

@type

The type of the serialized message.

string

key

additional properties

any

Example ^generated

{
  "code": 1,
  "message": "example",
  "details": [
    {
      "@type": "example"
    }
  ]
}