Download the PHP package beaub/laravel-easypost-webhooks without Composer

Handle Easypost Webhooks in a Laravel application

EasyPost can notify your application of events using webhooks. This package can help you handle those webhooks. All valid calls will be logged to the database. You can easily define jobs or events that should be dispatched when specific events hit your app.

This package will not handle what should be done after the webhook request has been validated and the right job or event is called. You should still code up any work yourself.

Before using this package we highly recommend reading the entire documentation on webhooks over at EasyPost.

Installation

You can install the package via composer:

The service provider will automatically register itself.

You must publish the config file with:

This is the contents of the config file that will be published at config/easypost-webhooks.php:

Next, you must publish the migration with:

After the migration has been published you can create the easypost_webhook_calls table by running the migrations:

Finally, take care of the routing: At the Easypost dashboard you must configure at what url Eaypost webhooks should hit your app. In the routes file of your app you must pass that route to Route::easypostWebhooks:

Behind the scenes this will register a POST route to a controller provided by this package. Because Easypost has no way of getting a csrf-token, you must add that route to the except array of the VerifyCsrfToken middleware:

Usage

Easypost will send out webhooks for several event types. You can find the full list of events types in the Easypost documentation.

Unlike Stripe, Easypost does not sign the webhooks it sends to your server. In order to ensure that requests are valid, use Basic Authentication and HTTPS on your endpoint. This package does not include this functionality. Refer to the Lavavel documentation regarding [Basic Authentication] (https://laravel.com/docs/5.5/authentication#http-basic-authentication) to secure your endpoint.

Unless something goes terribly wrong, this package will always respond with a 200 to webhook requests. Sending a 200 will prevent Easypost from resending the same event over and over again. All webhook requests will be logged in the easypost_webhook_calls table. The table has a payload column where the entire payload of the incoming webhook is saved.

If something goes wrong during the webhook request the thrown exception will be saved in the exception column. In that case the controller will send a 500 instead of 200.

There are two ways this package enables you to handle webhook requests: you can opt to queue a job or listen to the events the package will fire.

Handling webhook requests using jobs

If you want to do something when a specific event type comes in you can define a job that does the work. Here's an example of such a job:

We highly recommend that you make this job queueable, because this will minimize the response time of the webhook requests. This allows you to handle more Easypost webhook requests and avoid timeouts.

After having created your job you must register it at the jobs array in the easypost-webhooks.php config file. The key should be the name of the easypost event type where but with the . replaced by _. The value should be the fully qualified classname.

Handling webhook requests using events

Instead of queueing jobs to perform some work when a webhook request comes in, you can opt to listen to the events this package will fire. Whenever a valid request hits your app, the package will fire a easypost-webhooks::<name-of-the-event> event.

The payload of the events will be the instance of EasypostWebhookCall that was created for the incoming request.

Let's take a look at how you can listen for such an event. In the EventServiceProvider you can register listeners.

Here's an example of such a listener:

We highly recommend that you make the event listener queueable, as this will minimize the response time of the webhook requests. This allows you to handle more Easypost webhook requests and avoid timeouts.

The above example is only one way to handle events in Laravel. To learn the other options, read the Laravel documentation on handling events.

Advanced usage

Retry handling a webhook

All incoming webhook requests are written to the database. This is incredibly valuable when something goes wrong while handling a webhook call. You can easily retry processing the webhook call, after you've investigated and fixed the cause of failure, like this:

Performing custom logic

You can add some custom logic that should be executed before and/or after the scheduling of the queued job by using your own model. You can do this by specifying your own model in the model key of the easypost-webhooks config file. The class should extend BeauB\EasypostWebhooks\EasypostWebhookCall.

Here's an example:

Changelog

Please see CHANGELOG for more information about what has changed recently.

Testing

Contributing

Please see CONTRIBUTING for details.

Credits

This package was modified from the laravel-stripe-webhooks package and republished by Beau Buehler to work with the Easypost webhook.

Original Work:

• Freek Van der Herten
• All Contributors

A big thank you to Sebastiaan Luca who generously shared his Stripe webhook solution that inspired this package.

License

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