Libraries tagged by protocols
lucassmacedo/whatsapp-chat-api
3 Downloads
The SDK allows you to receive and send messages through your WhatsApp account. [Sign up now](https://app.chat-api.com/) The Chat API is based on the WhatsApp WEB protocol and excludes the ban both when using libraries from mgp25 and the like. Despite this, your account can be banned by anti-spam system WhatsApp after several clicking the "block" button.
lostping/otherserver
15 Downloads
Roundcube plugin to override predefined default hosts by adding an option to enter custom protocol, host and port
loper/minecraft-query-client
347 Downloads
Minecraft Query Client by TCP and UDP protocols.
loper/minecraft-php-structure
33 Downloads
Minecraft Structure Protocol & Version generator for PHP.
longitude-one/neo4j-bolt
413 Downloads
Neo4j Bolt Binary Protocol PHP Driver
lnx85/php-sbs-reader
19 Downloads
A PHP library that implements SBS-1 BaseStation protocol
littlesqx/spamassassin
8 Downloads
Spamd protocol client for PHP. PHP package that implements the spamd protocol specification
lightspeeddevelopment/lsx-geo-content
0 Downloads
LSX Geo Content allows you to serve different content to users based on their locations. This is automatically-detected by checking the users IP address and the Protocol Version (v4 or v6) being used.
levy/php-amqplib
739 Downloads
Formerly videlalvaro/php-amqplib. This library is a pure PHP implementation of the AMQP protocol. It's been tested against RabbitMQ.
lelush/laravel-apn-notification-channel
2 Downloads
Apple Push Notification Service (APNs) notifications channel for Laravel 5.3+ using the new APNs HTTP/2 protocol with token-based (JWT with p8 private key)
leibbrand-development/php-docker-client
22 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.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..." } ```
leberknecht/amqp-rpc-transporter-bundle
11022 Downloads
The bundle implements RPC functionality for AMQP protocol to the messenger component
laudis/graphaware-neo4j-bolt-legacy
13 Downloads
Neo4j Bolt Binary Protocol PHP Driver
kvazar/geminiapp
0 Downloads
KevaCoin Explorer for Gemini Protocol
kuvardin/firebase-http-api-fcm
9 Downloads
PHP SDK for HTTP Firebase Cloud Messaging Protocol