When using Lago, the app generates several events that you can listen to in order to trigger workflows. Each time an event is generated, you can view it in the Lago application using the webhook logs. This allows you to take a closer look at the generated events, detect possible errors, and retry them.
To add a webhook endpoint via the Lago app, follow these steps:
Note that you can add up to 10 webhook endpoints.
By creating a webhook endpoint, you have two signature options.
JWT
, with a possibly lengthy payload header and potential size limits;HMAC
, which features a shorter payload header and no size restrictions.Webhook endpoint signature
JWT
, with a possibly lengthy payload header and potential size limits;HMAC
, which features a shorter payload header and no size restrictions.Webhook endpoint signature
To find your HMAC signature token, navigate to Developers > Webhooks and locate the HMAC Signature Token. Then, reveal and copy the key.
Locate your HMAC siganture token
Once a webhook is registered in the app, you can access the webhook logs:
Webhook logs
You can see the details of a specific event by clicking on it. Depending on the event status, you will have access to two or three main blocks:
Your webhook server should response with a 2xx (200
, 201
, 202
, 204
) status code to acknowledge the receipt of the event. If the response is not supported as a success, Lago will consider it as failed.
Some events generated by Lago may not be received on the user side, which is why Lago displays an error status in the user interface.