---
title: "[Public Preview] Validate a Container Registry Name"
method: POST
path: "/v2/registries/validate-name"
tags: ["DigitalOcean-public.v2-new_Container Registries"]
---

# [Public Preview] Validate a Container Registry Name

`POST /v2/registries/validate-name`

To validate that a container registry name is available for use, send a POST
request to `/v2/registries/validate-name`.

If the name is both formatted correctly and available, the response code will
be 204 and contain no body. If the name is already in use, the response will
be a 409 Conflict. 

It is similar to `/v2/registry/validate-name` and exists for backward compatibility.

## Request body

- ValidateRegistry
  - `name` string, required — A globally unique name for the container registry. Must be lowercase and be composed only of numbers, letters and `-`, up to a limit of 63 characters.

## Response `204`

The action was successful and the response body is empty.

## Other responses

- `401` — Authentication failed due to invalid credentials.
- `409` — The request could not be completed due to a conflict.
- `429` — The API rate limit has been exceeded.
- `500` — There was a server error.
- `default` — There was an unexpected error.

## Changes

- **2025-10-16** `cb3bf9b21459` — 2 info
  - api tag `DigitalOcean-public.v2-new_Container Registries` added
  - api tag `Container Registries` removed
- **2025-07-18** `f8e8c290636c` — 1 info
  - endpoint added
- **2025-07-17** `5fc9af728e82` — 1 breaking
  - api path removed without deprecation
- **2025-07-17** `f8e8c290636c` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/digitalocean/apis/digitalocean-api/changes/v2/registries/validate-name/post.md)

---

[API](https://skmtc.dev/digitalocean/apis/digitalocean-api.md) · [All operations](https://skmtc.dev/digitalocean/apis/digitalocean-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/digitalocean/digitalocean-api/revisions/cb3bf9b21459/schema)