Download the PHP package viezel/webhooks without Composer

On this page you can find all versions of the php package viezel/webhooks. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package webhooks

Webhooks for Laravel

Latest Version on Packagist GitHub Tests Action Status

Simple and powerful implementation of Webhooks.

Installation

You can install the package via composer:

You can publish and run the migrations with:

Add routes to your application. Below is a typical route configuration with auth, api prefix and naming.

Usage

First, register Events in your application that should be exposed as Webhooks. To do so, your Events should implement the ShouldDeliverWebhooks interface.

The interface has two methods, getWebhookName for giving the webhook a unique name, and getWebhookPayload to define the data send with the webhook.

The following example shows how a Post Updated Event and its implementation:

Next you need to register all your events with the WebhookRegistry. This is typically done in the boot method of a ServiceProvider.

To check everything works as expected, go visit the webhooks events route. The default route is: /api/hooks/events. It depends how you register the webhook routes.

List available webhooks events

GET https://myapp.test/api/hooks/events

List registered webhooks

GET https://myapp.test/api/hooks

Register a webhook

POST https://myapp.test/api/hooks

Delete a webhook

DELETE https://myapp.test/api/hooks/{id}

Testing

Credits

License

The MIT License (MIT). Please see License File for more information.


All versions of webhooks with dependencies

PHP Build Version
Package Version
Requires php Version ^7.4
illuminate/contracts Version ^8.0
illuminate/queue Version ^8.0
illuminate/support Version ^8.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package viezel/webhooks contains the following files

Loading the files please wait ....