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

Vultr Container Registry API

Store and manage public and private container images for rapid deployment to Vultr Managed Kubernetes.

Vultr Container Registry API is one of 46 APIs that Vultr publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 12 JSON Schema definitions.

Tagged areas include Container Registry. The published artifact set on APIs.io includes an OpenAPI specification and 12 JSON Schemas.

This API exposes 13 operations across 9 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.vultr.com/v2.

13 operations 9 paths 26 schemas 2 DELETE6 GET2 OPTIONS1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.vultr.com/v2
Authentication
HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Vultr Container Registry API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (API_Key). It accepts HTTP bearer tokens (API Key). By default, every request must be authenticated.

  • API_Key — The Vultr API v2 uses API keys for authentication. You can manage your API keys in the Vultr customer portal. Please do not share API keys publicly, or embed t…
  • API Key — The Vultr API v2 uses API keys for authentication. You can manage your API keys in the Vultr customer portal. Please do not share API keys publicly, or embed t…

Paths & Operations 13

Across 9 paths, the API surfaces 13 operations — 2 DELETE, 6 GET, 2 OPTIONS, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Container Registry 13

Store and manage public and private container images for rapid deployment to Vultr Managed Kubernetes.

GET
/registries
List Container Registries
list-registries → 200401404422
POST
/registry
Create Container Registry
create-registry body → 201401422
DELETE
/registry/{registry-id}
Delete Container Registry
delete-registry 1 param → 204401404422
GET
/registry/{registry-id}
Read Container Registry
read-registry 1 param → 200401404422
PUT
/registry/{registry-id}
Update Container Registry
update-registry 1 param body → 200401404422
GET
/registry/{registry-id}/repositories
List Repositories
list-registry-repositories 1 param → 200401404422
DELETE
/registry/{registry-id}/repository/{repository-image}
Delete Repository
delete-repository 2 params → 204401404422
GET
/registry/{registry-id}/repository/{repository-image}
Read Repository
read-registry-repository 2 params → 200401404422
PUT
/registry/{registry-id}/repository/{repository-image}
Update Repository
update-repository 2 params body → 200401404422
OPTIONS
/registry/{registry-id}/docker-credentials?expiry_seconds=0&read_write=false
Create Docker Credentials
create-registry-docker-credentials 3 params → 200401404422
OPTIONS
/registry/{registry-id}/docker-credentials/kubernetes?expiry_seconds=0&read_write=false&base64_encode=false
Create Docker Credentials for Kubernetes
create-registry-kubernetes-docker-credentials 4 params → 200401404422
GET
/registry/region/list
List Registry Regions
list-registry-regions → 200401422
GET
/registry/plan/list
List Registry Plans
list-registry-plans → 200401422

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are registry-region (8 properties), registry (8 properties), registry-repository (7 properties), registry-user (6 properties). Each schema is shown below with its type and property counts.

registry_docker_credentials_auths__registry_region_name__vultrcr_com
object
This object represents the auth for this region
1 property
registry
object
Container Registry Entity
8 properties
registry-repository
object
Container Registry Repository Entity
7 properties
list_registry_repositories_200_response
object
2 properties
registry_metadata_subscription
object
Subscription information
1 property
registry_metadata
object
The metadata containing subscription information such as the region where this registry lives and monthly price and pending charges
2 properties
registry-kubernetes-docker-credentials
object
Container Registry Kubernetes Docker Credentials Entity
5 properties
meta_links
object
Cursor values for pagination.
2 properties
create_registry_request
object
4 properties 4 required
registry-user
object
Container Registry User Entity
6 properties
list_registry_plans_200_response_plans
object
4 properties
registry-plan
object
Container Registry Plan Entity. The KEY of this entity is the Plan ID you will use to create/upgrade your Container Registry
3 properties
registry_kubernetes_docker_credentials_data
object
1 property
list_registry_plans_200_response
object
1 property
list_registry_regions_200_response
object
2 properties
registry_metadata_subscription_billing
object
Billing information
2 properties
update_registry_request
object
2 properties
registry-storage
object
Container Registry Storage Information
5 properties
list_registries_200_response
object
2 properties
meta
object
The meta information object. See [Meta and Pagination](section/Introduction/Meta-and-Pagination) for more information.
2 properties
update_repository_request
object
1 property
registry_kubernetes_docker_credentials_metadata
object
1 property
registry-region
object
Container Registry Region Entity
8 properties
registry-docker-credentials
object
Container Registry Docker Credentials Entity
1 property
registry_docker_credentials_auths
object
Contains a single object with the key being the URN of the region
1 property
registry_storage
object
The allowed and used storage for this registry subscription.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vultr-container-registry-api-openapi.yml Raw ↑

Other APIs Vultr publishes across the network.

Vultr Account API
Vultr Application API
Vultr Backup API
Vultr Baremetal API
Vultr Billing API
Vultr Block API
Vultr Dns API
Vultr Firewall API
Vultr IAM Assumed Roles API
Vultr IAM Endpoint Actions API
Vultr IAM Groups API
Vultr IAM Policies API
Where this information came from

This is an independent, third-party profile of Vultr Container 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.