Webhooks

​

Adding a webhook URL

LAGO_URL="https://api.getlago.com"
API_KEY="__YOUR_API_KEY__"

curl --location --request POST "$LAGO_URL/api/v1/webhook_endpoints" \
  --header "Authorization: Bearer $API_KEY" \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "webhook_endpoint": {
      "name": "Production endpoint",
      "webhook_url": "https://foo.bar",
      "signature_algo": "hmac",
      "event_types": ["invoice.created", "invoice.payment_failure"]
    }
  }'

​

The webhook signature

• Dashboard
• API

• JWT embeds the payload in the signature header, so the header can grow large and some servers reject it;
• HMAC sends a short signature header, so header size is never an issue.

Set signature_algo to jwt or hmac in the create call.

​

Locate your HMAC signature token

​

Accessing the webhook logs

1. Go to the Developers section via the sidebar;
2. Open the Webhooks tab;
3. Click the webhook endpoint, then open the Deliveries tab to see the list of events;
4. Filter events by dates, types, HTTP status and status; and
5. Click Refresh to load new events (optional).

​

Accessing a specific event

1. A list of properties, including:
   1. Timestamp: the timestamp of the event;
   2. Webhook URL: the URL used to listen to events;
   3. Unique key: idempotency key associated with the event;
   4. Webhook type: the webhook type used to understand the action triggered;
   5. Response: the response code (i.e. acknowledgment of receipt);
   6. Number of retries: if the event failed, the number of retries attempted;
2. A JSON snippet with the arguments sent by Lago; and
3. The error response, when the event failed.

​

Errors and retries