Libraries tagged by api response json
mmockelyn/api-response
6 Downloads
Simple Laravel package to return Json responses.
messere/partial-response-middleware
0 Downloads
Filter out not needed fields from API response.
matthewbaggett/docker-api-php-client
5 Downloads
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..." } ```
masudrana/api-response
12 Downloads
Simple Laravel package to return Json responses.
lucasandrade/laravel-apiresponse
748 Downloads
Biblioteca de padronização de resposta em json
lordsling/api-response
22 Downloads
lmamsdev/json-response-three
1 Downloads
a simple class that returns a properly formatted json response with HTTP status
ilyatos/laravel-api-response
0 Downloads
Give it to me as JSON!
hauerheinrich/typo3_monitor_api
0 Downloads
Hauer-Heinrich - TYPO3 monitor api - allows to retrieve various information about the installed TYPO3 cms (response: json).
francscafe/json-response
468 Downloads
A simple class that returns a propely formatted json response with HTTP status
eozden/api-response
28 Downloads
Laravel api response macros
entrio/apiresponse
15 Downloads
A simple library that makes it easier to wort with JSON APIs
ellipse-online/json-response
3 Downloads
A simple class that returns a properly formatted json response with HYTP status
edsonr-coosta/response-json
12 Downloads
O Projeto Response é uma biblioteca PHP para criar respostas JSON com códigos de status HTTP personalizados, simplificando o desenvolvimento de APIs web eficazes em projetos PHP.
devcat/json-response
4 Downloads
A simple class that returnas a properly formatted json response with HTTP status