Send webhooks in Laravel apps

1.4.2 2021-10-22 00:20 UTC

This package is auto-updated.

Last update: 2022-06-22 01:49:30 UTC


Latest Version on Packagist Build Status Quality Score StyleCI Total Downloads

A webhook is a way for an app to provide information to another app about a particular event. The way the two apps communicate is with a simple HTTP request.

This package allows you to configure and send webhooks in a Laravel app easily. It has support for signing calls, retrying calls and backoff strategies.

If you need to receive and process webhooks take a look at our laravel-webhook-client package.


You can install the package via composer:

composer require spatie/laravel-webhook-server

You can publish the config file with:

php artisan vendor:publish --provider="Directoryxx\WebhookServer\WebhookServerServiceProvider"

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

return [

     *  The default queue that should be used to send webhook requests.
    'queue' => 'default',

     * The default http verb to use.
    'http_verb' => 'post',

     * This class is responsible for calculating the signature that will be added to
     * the headers of the webhook request. A webhook client can use the signature
     * to verify the request hasn't been tampered with.
    'signer' => \Directoryxx\WebhookServer\Signer\DefaultSigner::class,

     * This is the name of the header where the signature will be added.
    'signature_header_name' => 'Signature',

     * These are the headers that will be added to all webhook requests.
    'headers' => [],

     * If a call to a webhook takes longer that this amount of seconds
     * the attempt will be considered failed.
    'timeout_in_seconds' => 3,

     * The amount of times the webhook should be called before we give up.
    'tries' => 3,

     * This class determines how many seconds there should be between attempts.
    'backoff_strategy' => \Directoryxx\WebhookServer\BackoffStrategy\ExponentialBackoffStrategy::class,

     * By default we will verify that the ssl certificate of the destination
     * of the webhook is valid.
    'verify_ssl' => true,

By default, the package uses queues to retry failed webhook requests. Be sure to set up a real queue other than sync in non-local environments.


This is the simplest way to call a webhook:

   ->payload(['key' => 'value'])

This will send a post request to The body of the request will be JSON encoded version of the array passed to payload. The request will have a header called Signature that will contain a signature the receiving app can use to verify the payload hasn't been tampered with.

If the receiving app doesn't respond with a response code starting with 2, the package will retry calling the webhook after 10 seconds. If that second attempt fails, the package will attempt to call the webhook a final time after 100 seconds. Should that attempt fail, the FinalWebhookCallFailedEvent will be raised.

How signing requests works

When setting up, it's common to generate, store, and share a secret between your app and the app that wants to receive webhooks. Generating the secret could be done with Illuminate\Support\Str::random(), but it's entirely up to you. The package will use the secret to sign a webhook call.

By default, the package will add a header called Signature that will contain a signature the receiving app can use the payload hasn't been tampered with. This is how that signature is calculated:

// payload is the array passed to the `payload` method of the webhook
// secret is the string given to the `signUsingSecret` method on the webhook.

$payloadJson = json_encode($payload); 

$signature = hash_hmac('sha256', $payloadJson, $secret);

Customizing signing requests

If you want to customize the signing process, you can create your own custom signer. A signer is any class that implements Directoryxx\WebhookServer\Signer.

This is what that interface looks like.

namespace Directoryxx\WebhookServer\Signer;

interface Signer
    public function signatureHeaderName(): string;

    public function calculateSignature(array $payload, string $secret): string;

After creating your signer, you can specify it's class name in the signer key of the webhook-server config file. Your signer will then be used by default in all webhook calls.

You can also specify a signer for a specific webhook call:


If you want to customize the name of the header, you don't need to use a custom signer, but you can change the value in the signature_header_name in the webhook-server config file.

Retrying failed webhooks

When the app to which we're sending the webhook fails to send a response with a 2xx status code the package will consider the call as failed. The call will also be considered failed if the remote app doesn't respond within 3 seconds.

You can configure that default timeout in the timeout_in_seconds key of the webhook-server config file. Alternatively, you can override the timeout for a specific webhook like this:


When a webhook call fails, we'll retry the call two more times. You can set the default amount of times we retry the webhook call in the tries key of the config file. Alternatively, you can specify the number of tries for a specific webhook like this:


To not hammer the remote app we'll wait some time between each attempt. By default, we wait 10 seconds between the first and second attempt, 100 seconds between the third and the fourth, 1000 between the fourth and the fifth and so on. The maximum amount of seconds that we'll wait is 100 000, which is about 27 hours. This behavior is implemented in the default ExponentialBackoffStrategy.

You can define your own backoff strategy by creating a class that implements Directoryxx\WebhookServer\BackoffStrategy\BackoffStrategy. This is what that interface looks like:

namespace Directoryxx\WebhookServer\BackoffStrategy;

interface BackoffStrategy
    public function waitInSecondsAfterAttempt(int $attempt): int;

You can make your custom strategy the default strategy by specifying it's fully qualified class name in the backoff_strategy of the webhook-server config file. Alternatively, you can specify a strategy for a specific webhook like this.


Under the hood, the retrying of the webhook calls is implemented using delayed dispatching. Amazon SQS only has support for a small maximum delay. If you're using Amazon SQS for your queues, make sure you do not configure the package in a way so there are more than 15 minutes between each attempt.

Customizing the HTTP verb

By default, all webhooks will use the post method. You can customize that by specifying the HTTP verb you want in the http_verb key of the webhook-server config file.

You can also override the default for a specific call by using the useHttpVerb method.


Adding extra headers

You can use extra headers by adding them to the headers key in the webhook-server config file. If you want to add additional headers for a specific webhook, you can use the withHeaders call.

        'Another Header' => 'Value of Another Header'

Verifying the SSL certificate of the receiving app

When using an URL that starts with https:// the package will verify if the SSL certificate of the receiving party is valid. If it is not, we will consider the webhook call failed. We don't recommend this, but you can turn off this verification by setting the verify_ssl key in the webhook-server config file to false.

You can also disable the verification per webhook call with the doNotVerifySsl method.


Adding meta information

You can add extra meta information to the webhook. This meta information will not be transmitted, and it will only be used to pass to the events this package fires.

This is how you can add meta information:


Adding tags

If you're using Laravel Horizon for your queues, you'll be happy to know that we support tags.

To add tags to the underlying job that'll perform the webhook call, simply specify them in the tags key of the webhook-server config file or use the withTags method:



The package fires these events:

  • WebhookCallSucceededEvent: the remote app responded with a 2xx response code.
  • WebhookCallFailedEvent: the remote app responded with a non 2xx response code, or it did not respond at all
  • FinalWebhookCallFailedEvent: the final attempt to call the webhook failed.

All these events have these properties:

  • httpVerb: the verb used to perform the request
  • webhookUrl: the URL to where the request was sent
  • payload: the used payload
  • headers: the headers that were sent. This array includes the signature header
  • meta: the array of values passed to the webhook with the meta call
  • tags: the array of tags used
  • attempt: the attempt number
  • response: the response returned by the remote app. Can be an instance of \GuzzleHttp\Psr7\Response or null.


composer test


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


Please see CONTRIBUTING for details.


If you discover any security-related issues, please email instead of using the issue tracker.


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.

Our address is: Spatie, Samberstraat 69D, 2060 Antwerp, Belgium.

We publish all received postcards on our company website.


Support us

Spatie is a web design agency based in Antwerp, Belgium. You'll find an overview of all our open source projects on our website.

Does your business depend on our contributions? Reach out and support us on Patreon. All pledges will be dedicated to allocating workforce on maintenance and new awesome stuff.


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