Libraries tagged by cells

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

Easily use standard HTTP Controllers for API calls as well when using inertia as front end

Go to Download

Abstract classes for creating post types, taxonomies, metaboxes and ajax calls.

Go to Download

Wrapper around Nyholm\Psr7 library with a few helper methods and a basic emitter. For use in WordPress during ajax calls.

Go to Download

A simple form field creator ideal for wp-admin hook calls where a simple input is needed only as html.

Go to Download

Helps make your Wayapay api calls with PHP.

Go to Download

Helps make your Rexpay api calls with PHP.

Go to Download

PHPTerminal is a CLI application to make calls using predefined commands. It runs continuously giving the user a feeling of working on a Unix terminal.

Go to Download

PHPStan Plugin to collect method-calls for further processing

Go to Download

Temperature ValueObject for PHP. Easy to use with implementation of Kelvin, Celsius and Fahrenheit

Go to Download

Paga has made it very easy for businesses to accept payments.This Business Service Library is a Laravel/PHP module that helps you make API calls when processing Paga Business Transactions.

Go to Download

A wrapper to simplify calls to Google Ads API Client Library for PHP

Go to Download

Kazoo Wrapper for easy Kazoo API calls

Go to Download

Shortcut for making http api calls

Go to Download

PHPFirewall is a tool to allow/block connections to your web resource using IP address. The IP address details are either retrieved from local database or by making API calls to IP2Location.io

Go to Download