How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

GoHarbor Artifact API

The artifact API from GoHarbor — 9 operation(s) for artifact.

GoHarbor Artifact API is one of 38 APIs that GoHarbor publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Artifact. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 12 operations across 9 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against 2 base URLs: http://localhost/api/v2.0, https://localhost/api/v2.0.

12 operations 9 paths 18 schemas 3 DELETE6 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://{host}/api/v2.0
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

GoHarbor Artifact API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basic). By default, every request must be authenticated, though some operations may also be called without credentials.

Paths & Operations 12

Across 9 paths, the API surfaces 12 operations — 3 DELETE, 6 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Artifact 12
GET
/projects/{project_name}/repositories/{repository_name}/artifacts
List artifacts
listArtifacts 15 params → 200400401403404422500
POST
/projects/{project_name}/repositories/{repository_name}/artifacts
Copy artifact
CopyArtifact 4 params → 201400401403404405500
GET
/projects/{project_name}/repositories/{repository_name}/artifacts/{reference}
Get the specific artifact
getArtifact 15 params → 200400401403404500
DELETE
/projects/{project_name}/repositories/{repository_name}/artifacts/{reference}
Delete the specific artifact
deleteArtifact 4 params → 200401403404500
POST
/projects/{project_name}/repositories/{repository_name}/artifacts/{reference}/tags
Create tag
createTag 4 params body → 201400401403404405409500
GET
/projects/{project_name}/repositories/{repository_name}/artifacts/{reference}/tags
List tags
listTags 9 params → 200400401403404422500
DELETE
/projects/{project_name}/repositories/{repository_name}/artifacts/{reference}/tags/{tag_name}
Delete tag
deleteTag 5 params → 200401403404500
GET
/projects/{project_name}/repositories/{repository_name}/artifacts/{reference}/accessories
List accessories
listAccessories 8 params → 200400401403404500
GET
/projects/{project_name}/repositories/{repository_name}/artifacts/{reference}/additions/vulnerabilities
Get the vulnerabilities addition of the specific artifact
getVulnerabilitiesAddition 5 params → 200400401403404500
GET
/projects/{project_name}/repositories/{repository_name}/artifacts/{reference}/additions/{addition}
Get the addition of the specific artifact
getAddition 5 params → 200400401403404422500
POST
/projects/{project_name}/repositories/{repository_name}/artifacts/{reference}/labels
Add label to artifact
addLabel 4 params body → 200400401403404409500
DELETE
/projects/{project_name}/repositories/{repository_name}/artifacts/{reference}/labels/{label_id}
Remove label from artifact
removeLabel 5 params → 200401403404409500

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are Artifact (23 properties), Accessory (10 properties), NativeReportSummary (9 properties), Label (8 properties). Each schema is shown below with its type and property counts.

Tag
object
7 properties
Scanner
object
3 properties
Errors
object
The error array that describe the errors got during the handling of request
1 property
ExtraAttrs
object
Platform
object
5 properties
SBOMOverview
object
The generate SBOM overview information
7 properties
AdditionLink
object
2 properties
Error
object
a model for all the error response coming from harbor
2 properties
Accessory
object
The accessory of the artifact
10 properties
NewTag
object
The request body for creating a tag
1 property 1 required
Label
object
8 properties
NativeReportSummary
object
The summary for the native report
9 properties
ScanOverview
object
The scan overview attached in the metadata of tag
Annotations
object
Artifact
object
23 properties
AdditionLinks
object
VulnerabilitySummary
object
VulnerabilitySummary contains the total number of the foun d vulnerabilities number and numbers of each severity level.
3 properties
Reference
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

goharbor-artifact-api-openapi.yml Raw ↑

Other APIs GoHarbor publishes across the network.

GoHarbor Health API
GoHarbor Replication API
GoHarbor Scan API
GoHarbor Search API
GoHarbor Configure API
GoHarbor Gc API
GoHarbor Icon API
GoHarbor Immutable API
GoHarbor Label API
GoHarbor Ldap API
GoHarbor Member API
GoHarbor Oidc API
Where this information came from

This is an independent, third-party profile of GoHarbor Artifact API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.