Shell Python Node PHP C# Ruby


Registering a Webhook

curl "" \
    -u secret_key_3bW9JMZtPVDOfFNzwRdfE: \
    -d trigger="payment" \
    -d url=""
webhook = pl.Webhook.create(
webhook = Payload::Webhook.create(
    trigger: 'payment',
    url: ''
$webhook = Payload\Webhook::create(array(
    'trigger' => 'payment',
    'url' => ''
    trigger: 'payment',
    url: ''
var webhook = pl.Webhook.create(new {

Webhooks can be used to monitor events in real-time by initiating an HTTP request to any specified url providing an instant notification of that event.

Webhooks are useful in a variety of use-cases. Workflows that are asynchronous are a great example of where a webhook can be very useful. Some asynchronous workflows include automatic payments that are triggered at a certain date, and time in the future, waiting for a resulting payment from a payment link, watching for live updates on the status of a processing account, or to monitor for rejected transactions.

See a full list of available webhooks

Webhook logs

Get webhook including logs

curl "" \
    -G \
    -u secret_key_3bW9JMZtPVDOfFNzwRdfE: \
    -d "fields=*,logs"
webhook ='*', 'logs')\
webhook ='*', 'logs')
$webhook = Payload\Webhook::seelct(['*', 'logs'])
?>'*', 'logs')
var webhook ="*", "logs")

Webhook-related issues can be tricky to debug because of their asynchronous nature. To get a full list of triggered webhook events, you can request the full webhook log that will include the date, time, url, type of trigger, object that generated the trigger and the resulting http status from the url.

    "object": "webhook_log",

    // The type of trigger
    "trigger": "payment",

    // The date and time of the trigger
    "created_at": "2021-07-07 23:19:32",

    // The object that triggered the webhook
    "triggered_on": {
        "id": "txn_3bW9JN4BVk3wU0ZZQs2Ay",
        "object": "transaction",

    // The resulting http status code from the url
    "http_status": 200,

    // The url that the webhook triggered
    "url": ""