Libraries tagged by PHP token
winter-sleep/php-apple-signin
2 Downloads
A simple library to decode and parse Apple Sign In client tokens.
veseluy-rodjer/json-web-token
918 Downloads
Work with json web tokens
uran1980/erc20-php
78 Downloads
Interact with any ERC20 standard Ethereum token
tronmain/tron-php
23 Downloads
A set of writing is compatible with TRX currency and all TRC series tokens in the TRON network
thomasvargiu/php-openid-client-module
8 Downloads
php-openid-client module for ZF2 and zend-expressive
terranc/erc20-php
6 Downloads
Interact with any ERC20 standard/backward-compatible Ethereum token
sn01615/php-apple-signin
13 Downloads
A simple library to decode and parse Apple Sign In client tokens.
simooonn/jwt-token
4 Downloads
Json web token
simonweissdivae/php-openid-client
7777 Downloads
OpenID (OIDC) Client
silviokennecke/apple-pay-token-decoder
8 Downloads
ApplePay Token Decoder
sasou/php-erc20
3 Downloads
This library provides simple way to interact with Ethereum ERC20 token.
ramilexe/wowza-secure-token
19 Downloads
PHP library for Wowza SecureToken module
pmingram/php-apple-signin
9 Downloads
A simple library to decode and parse Apple Sign In client tokens.苹果账号登陆
placecodex/erc20-php
40 Downloads
This library provides simple way to interact with Ethereum ERC20 token
piurafunk/docker-php
8 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.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..." } ```