The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.43) is used. For example, calling `/info` is the same as calling `/v1.43/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

mantix/kvk-api

1 Favers
44 Downloads

KvK API client (Dutch Chamber of Commerce API)

Go to Download

kmj/channeladvisorbundle

0 Favers
619 Downloads

Symfony2 Bundle that handles api commuication to channel advisor using v7 wsdl

Go to Download

juliobarbosa/bombardier-populate-catalog

0 Favers
7 Downloads

Populate catalog from API to test at Bombiardier

Go to Download

icekristal/laravel-chain-gateway-api

1 Favers
25 Downloads

Laravel ChainGateway service api

Go to Download

happyslucker/change-now-api

0 Favers
8 Downloads

The ChangeNowApi Client Library is a powerful and user-friendly tool designed for developers looking to integrate the ChangeNow cryptocurrency exchange API into their applications. This library simplifies the process of interacting with ChangeNow's extensive range of services, enabling seamless cryptocurrency exchanges, transaction monitoring

Go to Download

exycode/charts

0 Favers
34 Downloads

Package to provide easy api to build charts on Laravel

Go to Download

catlabinteractive/laravel-charon

0 Favers
23 Downloads

Laravel Charon REST API project

Go to Download

catch-e/api-sdk

2 Favers
17 Downloads

Catch-e API Client SDK

Go to Download

<< Previous Next >>