Docker Hub access-tokens API
The Personal Access Token endpoints lets you manage personal access tokens. For more information, see [Access Tokens](https://docs.docker.com/security/access-tokens/).You can use a personal access token instead of a password in the [Docker CLI](https://docs.docker.com/engine/reference/commandline/cli/) or in the [Create an authentication token](#operation/PostUsersLogin) route to obtain a bearer token.### ScopesFor each scope grouping (in this case "repo"), you only need to define 1 scope as any lower scopes are assumed.For example: If you define `repo:write`, the API assumes the scope of both `repo:read` *and* `repo:public_read` as well.If you were to define both `repo:write` *and* `repo:read`, then `repo:read` is assumed by `repo:write` and ignored.***Treat your personal access token like your password and keep it secret. You cannot retrieve your token after it is generated.***
Docker Hub access-tokens API is one of 10 APIs that Docker Hub publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Access Tokens. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.
This API exposes 5 operations across 2 paths, and defines 8 schemas. It is described by OpenAPI 3.0.3, at version 2-beta.
Requests are made against a single base URL, https://hub.docker.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Docker Hub access-tokens API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (bearerAuth).
It accepts HTTP bearer tokens (bearerSCIMAuth).
Paths & Operations 5
Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
The Personal Access Token endpoints lets you manage personal access tokens. For more information, see [Access Tokens](https://docs.docker.com/security/access-tokens/). You can use…
Schemas 8
The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are accessToken (12 properties), getAccessTokensResponse (5 properties), createAccessTokenRequest (3 properties), patchAccessTokenRequest (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Docker Hub 9
Other APIs Docker Hub publishes across the network.
This is an independent, third-party profile of Docker Hub access-tokens API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.