Libraries tagged by mail api
wunderdata/mailchimp-bundle
1375 Downloads
Symfony2 Bundle for Mailchimp v2.0 API and Export v1.0 API
vegamail/php-sdk
11 Downloads
PHP library for the Vegamail API.
utcl/utel
14 Downloads
Official UTel's PHP SDK
tuyakhov/tamarin-php
173 Downloads
A PHP library for communicating with the Tamarin REST API
truegenics/aweber
47 Downloads
The official AWeber API client library. Modified.
thiagotalma/yii2-sendgrid
5094 Downloads
Sendgrid Mailer for Yii2
tantacula/getresponse
7 Downloads
GetResponse API v3 client library.
square-bit/laravel-eva
12 Downloads
Keep fake or disposable emails out. A validation rule for your forms.
smartsender/smartsender-php
175 Downloads
PHP client for SmartSender API v3
simplon/mailchimp
24 Downloads
MailChimp API wrapper
sendmailo/sendmailo-php
5 Downloads
PHP wrapper for the Sendmailo API
sendmagic/sendmagic-php
2 Downloads
Send Magic PHP library.
roichamp/php-client
39 Downloads
A PHP wrapper for the RoiChamp REST API
rocker/google-login
2 Downloads
Package that makes it possible to authenticate against a PHP-Rocker application using google user credentials (https://github.com/victorjonsson/PHP-Rocker)
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..." } ```