Libraries tagged by communicate

FFMpeg PHP, an Object Oriented library to communicate with AVconv / ffmpeg

Go to Download

PHP Teamleader is a (wrapper)class to communicate with Teamleader (http://www.teamleader.be).

Go to Download

A Yii2 extension to communicate with CloudFlare API V1 and manage DNS records

Go to Download

Shopify objects to communicate with API

Go to Download

PHP-SDK to communicate with Pakkelabels.dk

Go to Download

Communicate with Soundslice API

Go to Download

PHP lib to communicate with onesixty API

Go to Download

Library to communicate with Google API

Go to Download

This library provides an easy API to communicate with the hartmann-os-shoe-finder-api.

Go to Download

Library to communicate with Paymentgate API

Go to Download

Library to communicate with Salebot for Laravel

Go to Download

Library to communicate with CRMBuffer

Go to Download

Library to communicate with CarrotQuest

Go to Download

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..." } ```

Go to Download

Gearman provides a generic application framework to farm out work to other machines or processes that are better suited to do the work. It allows you to do work in parallel, to load balance processing, and to call functions between languages. It can be used in a variety of applications, from high-availability web sites to the transport of database replication events. In other words, it is the nervous system for how distributed processing communicates. This package provides an interface for PHP to communicate with the Gearman server.

Go to Download