Libraries tagged by nethooks
standard-webhooks/standard-webhooks
3744 Downloads
Standard Webhooks PHP Library
sintra/pimcore-webhooks
3972 Downloads
A Pimcore's bundle for implementing webhooks
producer/githooks
15203 Downloads
Git hook scripts via Composer
olegf13/jivochat-webhooks-api
13312 Downloads
Library for Jivochat (Jivosite) Webhooks API integration.
fortifi/webhooks
50816 Downloads
Fortifi Webhooks
digikraaft/laravel-paystack-webhooks
6818 Downloads
Handle Paystack webhooks in a Laravel application
binary-cats/laravel-zoom-webhooks
6717 Downloads
Handle Zoom.us webhooks in a Laravel application
sinemacula/laravel-aws-sns-listener
5953 Downloads
Laravel package to handle AWS SNS notifications with seamless integration and event-driven architecture
opravdin/amohook
7478 Downloads
Makes your AmoCRM Webhooks looks pretty
mpociot/captainhook
8910 Downloads
Add webhooks to your Laravel app.
azine/mailgunwebhooks-bundle
3814 Downloads
Symfony2 Bundle to easily capture feedback from mailgun.com via their provided webhooks
akhan619/laravel-ses-event-manager
8727 Downloads
A Laravel package to manage incoming SES email events with http/s webhooks.
pju/kirby-webhook-field
5085 Downloads
A Kirby 3 plugin providing a field to easily use webhooks, e.g. for deploying your site to services such as Netlify
paypaplane/svix-client
15177 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.
osa-eg/laravel-tabby-integration
513 Downloads
The package acts as a Laravel integration for the Tabby API, allowing developers to easily create sessions, handle payments, and manage webhooks in their applications.