Libraries tagged by subscribee
mailmotor/mailchimp-bundle
187135 Downloads
This Symfony2 bundle loads in MailChimp as a service. So you can subscribe/unsubscribe members to MailChimp.
coreproc/msisdn-ph
23216 Downloads
An MSISDN identification and cleaner library for Philippine telco subscribers
zwo3/newsletter_subscribe
3398 Downloads
Subscribe / Unsubscribe Extension (e.g. for Newsletter), depends on tt_address
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.
mydnic/laravel-subscribers
4518 Downloads
Easily Manage Internal Newsletter Subscribers in Laravel
mailcampaigns/module-subscriber-api
11272 Downloads
A module that extends the Magento 2 API to manage subscribers.
mperusso/nats
3853 Downloads
nats jetstream client for php compatible with php 7.3
morscate/laravel-event-flow
8426 Downloads
Event Flow helps you to create event driven applications with Laravel
migratorydata/migratorydata-client-php
21165 Downloads
MigratoryData Client API for PHP
kuria/event
16222 Downloads
Event library that implements variations of the mediator and observer patterns
g4/events
45985 Downloads
events php library
freddie/mercure-x
334 Downloads
A Mercure Hub PHP implementation.
cashier-provider/core
13424 Downloads
Cashbox provides an expressive, fluent interface to manage billing services.
verbb/back-in-stock
530 Downloads
Subscribe to out of stock products to receive an email when back in stock.
paypaplane/svix-client
13196 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.