How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Daytona docker-registry API

The docker-registry API from Daytona — 3 operation(s) for docker-registry.

Daytona docker-registry API is one of 28 APIs that Daytona publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include docker-registry. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and 2 JSON Schemas.

This API exposes 6 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 1.0.

Requests are made against a single base URL, https://app.daytona.io/api.

6 operations 3 paths 4 schemas 1 DELETE3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Base URL
https://app.daytona.io/api
Authentication
HTTP Bearer, OpenID Connect
License
Resource Areas
1

Authentication & Security 2

Daytona docker-registry API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearer). It supports OpenID Connect (oauth2) discovered at http://localhost:3000/.well-known/openid-configuration.

  • bearer — API Key access

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 3 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

docker-registry 6
POST
/docker-registry
Create registry
createRegistry 1 param body → 201
GET
/docker-registry
List registries
listRegistries 1 param → 200
GET
/docker-registry/registry-push-access
Get temporary registry access for pushing snapshots
getTransientPushAccess 2 params → 200
GET
/docker-registry/{id}
Get registry
getRegistry 2 params → 200
PATCH
/docker-registry/{id}
Update registry
updateRegistry 2 params body → 200
DELETE
/docker-registry/{id}
Delete registry
deleteRegistry 2 params → 204

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are DockerRegistry (8 properties), RegistryPushAccessDto (6 properties), CreateDockerRegistry (5 properties), UpdateDockerRegistry (5 properties). Each schema is shown below with its type and property counts.

UpdateDockerRegistry
object
5 properties 3 required
CreateDockerRegistry
object
5 properties 4 required
RegistryPushAccessDto
object
6 properties 6 required
DockerRegistry
object
8 properties 8 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

daytona-io-docker-registry-api-openapi.yml Raw ↑

Other APIs Daytona publishes across the network.

Daytona admin API
Daytona api-keys API
Daytona audit API
Daytona computer-use API
Daytona config API
Daytona file-system API
Daytona git API
Daytona Health API
Daytona info API
Daytona interpreter API
Daytona jobs API
Daytona lsp API
Where this information came from

This is an independent, third-party profile of Daytona docker-registry 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.