Libraries tagged by substrike

Cashbox provides an expressive, fluent interface to manage billing services.

Go to Download

WordPress factories for Test-driven development.

Go to Download

Server side of Wex live updates: Mercure topics, subscriber tokens and publication

Go to Download

MailChimp form finishers for subscribe and unsubscribe

Go to Download

MU plugin for class-based WordPress events, listeners, and subscribers.

Go to Download

Adds a custom field to UserForms which allows you to select a list from MailChimp and subscribe on submission.

Go to Download

Allows to implement subscription on Viber's account and broadcast notifications to different groups of subscribed userss,

Go to Download

Telegram bot for ensuring group access is limited to e.g. Twitch subscribers and/or Patreon supporters.

Go to Download

Persist messages and publish/subscribe them to/from a broker

Go to Download

Subscribe your Statamic v5 contact form submissions straight into Brevo

Go to Download

Newsletter Campaigns - TYPO3 newsletter extension with double opt-in subscriptions, subscriber groups, scheduled campaigns, FAL attachments, frontend archive and sg_mail queue delivery.

Go to Download

The Silverstripe Mailchimp Module enables you to keep your Mailchimp mailing list in sync with the subscribers and/or members of your Silverstripe website.

Go to Download

Improves the login screen and hides admin bar from subscribers, also redirects them to the home page upon login.

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

Firebase Cloud Messaging (HTTP v1) web push for Laravel — hand-signed OAuth2 JWT (no google/apiclient or kreait/firebase-php dependency), channel/audience-based subscriber targeting, and on-device diagnostics logging for mobile debugging.

Go to Download