Libraries tagged by Email Events

Small, simple, diverse PHP Toolkit for quick prototyping

Go to Download

Brevo (ex-Sendinblue) for Symfony: the official SDK on Symfony HttpClient, list/campaign commands, and webhook events re-dispatched for any listener.

Go to Download

A PHP lightweight Postal API Client

Go to Download

Email-based support tickets for Laravel. IMAP inbox sync, threading, drafts, lifecycle events and AI-powered similarity search.

Go to Download

Server-side client for Hermesi: publish events and read what became of them, keep subscribers in sync, send a direct message, mint subscriber tokens and preference links. Works with any PSR-18 HTTP client.

Go to Download

A PHP client for the SparkPost API - transmissions, message events and suppression - over any PSR-18 HTTP client

Go to Download

Handles mailer transport webhook callbacks for bounce and spam events in Mautic.

Go to Download

Sendy mailing list integration plugin for the MyAdmin control panel. Provides automated subscriber management via the Sendy API, including account-activation hooks and event-driven mailing list subscriptions.

Go to Download

Advanced, secure OTP (Email/SMS/WhatsApp) package for Laravel with hashed codes, TTL, rate limiting, one-time use, events, and drivers.

Go to Download

Provides a more flexible way of sending emails to event participant.

Go to Download

Observes Mautic contact, email, campaign, form, page and segment events and streams them to the Mautic Insights ingest API.

Go to Download

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.

Go to Download

A Laravel package to manage incoming SES email events with http/s webhooks.

Go to Download

Parses event data from a variety of email service providers

Go to Download

Laravel integration for GhostParse: a verified webhook route that turns inbound email into Laravel events.

Go to Download