Docker Hub API
GET /v2/repositories/{id}/{id} endpoint removal
Deprecated, no dateSubscribe to Docker Hub APIShare
Docker Hub API deprecated the GET /v2/repositories/{id}/{id} endpoint on September 19, 2025, without a shutdown date. Calls made to this endpoint are planned for removal and will fail. The change affects requests sent to the legacy repository path.
Calls it hits
GET /v2/repositories/{id}/{id}
What to use instead of these calls
Call GET /v2/namespaces/{namespace}/repositories/{repository} (Get repository) instead.
In Docker Hub API's words
GET /v2/repositories/{namespace}/{repository} replaced by Get repository
Facts
- API
- Docker Hub API
hub.docker.com - Kind
- Endpoint removal
- Announced
- September 19, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Docker Hub API's own pages
Questions
When does this change take effect?
Docker Hub API deprecated GET /v2/repositories/{id}/{id} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Docker Hub 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 Docker Hub API 4
-
No date
GET /v2/repositories/{id}Endpoint removal Deprecated, no date -
No date
HEAD /v2/repositories/{id}/{id}Endpoint removal Deprecated, no date -
No date
POST /v2/repositoriesEndpoint removal Deprecated, no date -
No date
POST /v2/repositories/{id}Endpoint removal 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.