> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/artifact-registry/3.0/reference/rest-api.md).

# REST API

Reference for the Harness Artifacts REST API, covering the base URL, authentication, common endpoints, rate limits, and the interactive API explorer.

The Harness Artifacts REST API lets you manage registries, artifacts, upstream proxies, lifecycle rules, and Dependency Firewall policy programmatically.

## Base URL

```
https://app.harness.io/har/api/v1
```

For self-managed deployments, replace `app.harness.io` with your on-prem hostname.

## Authentication

All requests require an API key in the `x-api-key` header:

```bash
curl -H "x-api-key: $HARNESS_API_KEY" \
  "https://app.harness.io/har/api/v1/registry?accountIdentifier=$HARNESS_ACCOUNT_ID"
```

Go to [Authentication and identity tokens](https://developer.harness.io/artifact-registry/3.0/concepts/authentication-and-identity-tokens.md) for guidance on generating a personal access token or service account token.

## Interactive API reference

Go to [Artifact Registry API Reference](https://developer.harness.io/artifact-registry/api-reference) for the full interactive OpenAPI explorer, including request and response schemas for every endpoint.

The Harness Artifacts (New Experience) API is an extension of the Harness Artifact Registry (Classic Experience) API. All Classic Experience API endpoints are available in the New Experience. New endpoints added in the New Experience API (Terraform Backend, Webhooks, Lifecycle Rules) appear in the same explorer once the spec is updated.

## Common operations

| Operation              | Method   | Path                                                            |
| ---------------------- | -------- | --------------------------------------------------------------- |
| List registries        | `GET`    | `/registry`                                                     |
| Create a registry      | `POST`   | `/registry`                                                     |
| Get a registry         | `GET`    | `/registry/{registryRef}`                                       |
| Update a registry      | `PUT`    | `/registry/{registryRef}`                                       |
| Delete a registry      | `DELETE` | `/registry/{registryRef}`                                       |
| List artifacts         | `GET`    | `/registry/{registryRef}/artifact`                              |
| Get artifact details   | `GET`    | `/registry/{registryRef}/artifact/{artifact}`                   |
| Delete an artifact     | `DELETE` | `/registry/{registryRef}/artifact/{artifact}`                   |
| List artifact versions | `GET`    | `/registry/{registryRef}/artifact/{artifact}/version`           |
| Get a version          | `GET`    | `/registry/{registryRef}/artifact/{artifact}/version/{version}` |
| Delete a version       | `DELETE` | `/registry/{registryRef}/artifact/{artifact}/version/{version}` |

The `registryRef` path parameter takes the format `<account_identifier>/<registry_identifier>/+` for account-scoped registries, `<account_identifier>/<org_identifier>/<registry_identifier>/+` for org-scoped, and `<account_identifier>/<org_identifier>/<project_identifier>/<registry_identifier>/+` for project-scoped. The trailing `/+` is required.

List-scoped endpoints (for example, `GET /registry` without a `registryRef`) scope the response using query parameters: `accountIdentifier`, `orgIdentifier`, and `projectIdentifier`.

## Rate limits

The REST API shares the Harness platform rate limit: 1,000 requests per minute per API key. Requests that exceed the limit return `429 Too Many Requests`. Retry with exponential back-off.

{% @harness-feedback/feedback %}
