Libraries tagged by engine Rest

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

A PHP framework without any strings attached, but with all the magical features.

Go to Download

A zero-dependency, upload-and-run PHP micro-framework for building REST APIs. Perfect for shared hosting.

Go to Download

A Laravel GraphQL-lite internal query engine — single endpoint, schema-driven, N+1-safe, mutation-ready.

Go to Download

Web request library providing GET PUT POST HEAD Cookies and more for file_get_contents

Go to Download

Modified version of slim/slim-skeleton with twig template engine

Go to Download

Restgrip view module based on Phalcon SimpleView and Volt template engine.

Go to Download

PHP client for Docker Engine REST API

Go to Download

Laravel package wrapper for Jasper Reporting Engine REST API

Go to Download

Cisco Identity Services Engine REST API Client

Go to Download

PHP REST Library for Wowza Streaming Engine

Go to Download

Commercial Magento 2 Surcharge extension — transparent cutting fees, oversized-shipping surcharges and category-based extra costs. Multi-rule engine, per-product override, bulk-assign, mixed-cart handling, country restrictions. Hyvä-compatible. Module source delivered after purchase.

Go to Download

ION Engine PHP Framework. A back-end framework for multi-app web apps and RESTful APIs

Go to Download

The most awesome validation engine ever created for PHP

Go to Download

PHP library to query and send RCON commands to servers based on "Source Engine Query" protocol

Go to Download