# /v2/registry is deprecated

DigitalOcean API deprecated /v2/registry* without giving a shutdown date yet.

DigitalOcean deprecated calls matching /v2/registry* without a shutdown date. Requests to these endpoints will eventually fail. The provider notes that this endpoint is deprecated and directs clients to alternative routes.

## What to use instead

Call the multi-registry endpoints under /v2/registries instead, such as GET /v2/registries/{registry_name} and /v2/registries/{registry_name}/repositoriesV2.

- API: DigitalOcean API (api.digitalocean.com)
- Kind: Endpoint removal
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/v2/registry*`
- Source: [Announcement](https://api-engineering.nyc3.digitaloceanspaces.com/spec-ci/DigitalOcean-public.v2.yaml)
- Verified: October 26, 2026, against DigitalOcean API's own pages
- Page: https://www.okapi.bot/providers/digitalocean/breaking-changes/v2-registry-is-deprecated/

## DigitalOcean API's words

> Note: This endpoint is deprecated. Please use the `/v2/registries` endpoint instead.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent