Libraries tagged by details

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.41) is used. For example, calling `/info` is the same as calling `/v1.41/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

The best way to get details about an IP address, no ext required

Go to Download

Berlin3 'Details' API Wrapper

Go to Download

YouTube Metadata normal grabs singular details about a video and its uploader.

Go to Download

Display “You will save x %” on the product details page in OXID eShop

Go to Download

A module for OXID eShop to round the price on product details page to five Rappen/Cent (whatever currency you use). Might be important for example for Switzerland (AKA CH)

Go to Download

Overly cautious HelloWorld class. See the repo for details.

Go to Download

This package can help you to website visitor details get using their Ip address

Go to Download

A small helper class to request package details from the Packagist API

Go to Download

Used for creating entity grids with search form and detail form. Designed for Nette.

Go to Download

contact form for sending email to admin and saving contact form details in database

Go to Download

A set of tools to make working with Dutch contact details easier in Laravel.

Go to Download

Verify Gravity Forms bank details with Loqate bank verification API.

Go to Download

PHP docBloc - Generate and keep updated docBlock of your project files fetching details from composer.json and Git. Supported filetypes: *.php, *.ini, *.sh, *.bat, *.md (No Composer or PEAR need to be installed to use this tool).

Go to Download

Look up car details from a number plate in many countries worldwide. Account required from www.vehicleregistrationapi.com

Go to Download