Libraries tagged by email library
oneup/mailchimp-api-v3
23456 Downloads
Simple PHP library for MailChimp API V3
mtymek/mt-mail
37199 Downloads
Zend Framework e-mail module. Using this library can easily create e-mail messages from PHTML templates (with optional layouts) and send them using configurable transports. Pluggable, EventManager-driven architecture allows you to customize every aspect of the process.
mmollick/drip-php
9423 Downloads
Community supported library for Drip.com's API
lasso/mail-parser-bundle
13409 Downloads
Parse mails using the Zend framework libraries
eliksir/sendgrid-subuser-api
13389 Downloads
Library to easily work with the SendGrid Subuser API
djagya/yii2-sparkpost
15658 Downloads
A library provides Yii2 integration with SparkPost mail service
beapp/mailer-transport-mailgun
5568 Downloads
Mailgun transport for Mailer library
beapp/mailer-core
7532 Downloads
Core mailer library
spinen/laravel-mail-assertions
109260 Downloads
PHPUnit mail assertions for testing email in Laravel.
hatxor/bot-framework-php
15072 Downloads
A complete bot framework library write in php, plug and play!
rezozero/subscribeme
1505 Downloads
Unified Email Service Library: A simple mailing list subscriber factory that includes a mailing list subscription feature and the ability to send transactional emails.
2lenet/hermes-bundle
6942 Downloads
Email sender library
reelworx/t3-mailservice
4089 Downloads
A library for TYPO3 extensions to conveniently send emails using Fluid templates with HTML and TXT content
paypaplane/svix-client
13200 Downloads
Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.
netherphp/email
1827 Downloads
An email library.