Libraries tagged by php email
pepipost/pepipost-mandrill-sdk-php
251 Downloads
MODIFIED - API client library for the Mandrill email as a service platform
notifea/notifea-php-laravel
180 Downloads
Laravel wrapper for PHP language for Notifea services.
nickyeoman/php-validation-class
120 Downloads
Validate, email, postal code, zipcode and phone numbers
nholdren/marketing-cloud-php-soap
18 Downloads
PHP library for interacting with the Salesforce Marketing Cloud SOAP API
narokishi/laravel-email-templates
182 Downloads
Laravel Email Templates (Blade)
mozgbrasil/magento-base-php_72
51 Downloads
Módulo base para Magento
mozgbrasil/magento-base-php_71
147 Downloads
Módulo base para Magento
mozgbrasil/magento-base-php_56
1233 Downloads
Módulo base para Magento
mozgbrasil/magento-base-php_54
228 Downloads
Módulo base para Magento
molajo/email
441 Downloads
Molajo Email: platform independent support with adapters for PHPMailer, SwiftMail, and native PHP mail
minerva22/ffa-jobs-emails
24 Downloads
PHP function to access ffa-jobs-settings API
metarush/email-fallback
135 Downloads
Send email via SMTP host, if it fails, fallback/failover to another SMTP host. Round-robin mode also available to distribute the load to all SMTP hosts.
messagex/php-sdk-common
4467 Downloads
Common libraries for MessageX PHP SDKs
maxvaer/docker-openapi-php-client
4 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..." } ```
mattmezza/php-mail-msg
14 Downloads
Need to send an email from your webserver's MTA using the mail() function??