Download the PHP package binary-cats/laravel-lob-webhooks without Composer

Handle Lob.com Webhooks in a Laravel application

Lob.com providers powerful set of APIs to handle personalized postcards, letters, and checks to customers with comprehensive per-piece mail tracking and analytics. Lob.com also can notify your application of mail events using webhooks. This package can help you handle those webhooks. Out of the box it will verify Lob.com signature of all incoming requests. 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 (eg. regarding payments) yourself.

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

This package is an almost line-to-line adapted copy of absolutely amazing spatie/laravel-stripe-webhooks. Give them your love!

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/lob-webhooks.php:

In the signing_secret key of the config file you should add a valid webhook secret. he secret is unique for each webhook and can be found in the details page for the respective webhook in the dashboard. webhook in the dashboard.

You can skip migrating is you have already installed Spatie\WebhookClient

Next, you must publish the migration with:

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

Routing

Finally, take care of the routing: At the Lob.com dashboard you must configure at what url Lob.com webhooks should hit your app. In the routes file of your app you must pass that route to Route::lobWebhooks():

I like to group functionality by domain, so would suggest webhooks/lob

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

Usage

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

Lob.com will sign all requests hitting the webhook url of your app. This package will automatically verify if the signature is valid. If it is not, the request was probably not sent by Lob.com.

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

If the signature is not valid, the request will not be logged in the webhook_calls table but a BinaryCats\LobWebhooks\Exceptions\WebhookFailed exception will be thrown. 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.

The package will ALWAYS cast events to lowercase - so your configured keys must be lowercase, too

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:

Spatie highly recommends that you make this job queueable, because this will minimize the response time of the webhook requests. This allows you to handle more Lob.com webhook requests and avoid timeouts.

After having created your job you must register it at the jobs array in the lob-webhooks.php config file. The key should be the name of Lob.com 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 lob-webhooks::<name-of-the-event> event.

The payload of the events will be the instance of WebhookCall 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:

Spatie highly recommends that you make the event listener queueable, as this will minimize the response time of the webhook requests. This allows you to handle more Lob.com 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 job class. You can do this by specifying your own job class in the process_webhook_job key of the lob-webhooks config file. The class should extend BinaryCats\LobWebhooks\ProcessLobWebhookJob.

Here's an example:

Handling multiple signing secrets

When needed might want to the package to handle multiple endpoints and secrets. Here's how to configurate that behaviour.

If you are using the Route::lobWebhooks macro, you can append the configKey as follows (assuming your incoming route url is webhooks/lob):

Alternatively, if you are manually defining the route, you can add configKey like so:

If this route parameter is present, the verify middleware will look for the secret using a different config key, by appending the given the parameter value to the default config key. E.g. If Lob.com posts to lob-webhook-url/my-named-secret you'd add a new config named signing_secret_my-named-secret.

Example config might look like:

About Lob.com

Lob.com provides APIs for businesses to increase the connectivity between the offline and online worlds.

Changelog

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

Testing

Contributing

Please see CONTRIBUTING for details.

Security

If you discover any security related issues, please email [email protected] instead of using issue tracker.

Postcardware

You're free to use this package, but if it makes it to your production environment we highly appreciate you sending us a postcard from your hometown, mentioning which of our package(s) you are using.

Credits

• Cyrill Kalita
• All Contributors

Big shout-out to Spatie for their work, which is a huge inspiration.

Support us

Binary Cats is a webdesign agency based in Illinois, US.

License

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