Libraries tagged by test server

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

Common components shared between leedavis81/drest (server) and leedavis81/drest-client libraries.

Go to Download

This package helps you to quickly build a REST API using the Laravel framework following the json:api specification.

Go to Download

This package helps you to quickly build a REST API using the Laravel framework following the json:api specification.

Go to Download

Authentication server compatible with OAuth2.

Go to Download

A Pusher bridge for Laravel 5+

Go to Download

A small PHP 7.0 Framework

Go to Download

A Laravel package that allows access to the API of your Jellyfin server.

Go to Download

Servidor REST para EUROGLAS

Go to Download

Laravel wrapper for the client part of the library to construct applications based on the server-to-server architecture.

Go to Download

The client part of the library to construct applications based on the server-to-server architecture.

Go to Download

This Package leverages oauth2-server-laravel and laravel-cors packages, and adds version control, and routes to implement all packages to have a fully functional API

Go to Download

The PSR RESTful Router Library

Go to Download

A Slim Framework skeleton powered by react http server

Go to Download

OAuth2 Core CodeIgniter 4 for project Codenom

Go to Download