/v2/registry* → endpoint removal
DigitalOcean API
Deprecated, no date
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.
Calls it hits
/v2/registry*
What to use instead of these calls
Call the multi-registry endpoints under /v2/registries instead, such as GET /v2/registries/{registry_name} and /v2/registries/{registry_name}/repositoriesV2.
In DigitalOcean API's words
Note: This endpoint is deprecated. Please use the `/v2/registries` endpoint instead.
Facts
- API
- DigitalOcean API
api.digitalocean.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against DigitalOcean API's own pages
Questions
When does this change take effect?
DigitalOcean API deprecated /v2/registry* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: DigitalOcean API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from DigitalOcean API 6
-
No date
Claude 3 OpusModel retirement Deprecated, no date -
No date
Claude 3.5 HaikuModel retirement Deprecated, no date -
No date
Claude 3.5 SonnetModel retirement Deprecated, no date -
No date
GPT-5.1-Codex-MaxModel retirement Deprecated, no date -
No date
Kimi K2.5Model retirement Deprecated, no date -
No date
Meta Llama 3.1 8B-InstructModel retirement Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.