Configuring a webhook
Pass awebhook_url when creating a table.
Webhook payload
Each delivery is a JSON POST request with the following structure.Headers
Every webhook request includes these headers:| Header | Description |
|---|---|
Content-Type | Always application/json. |
X-Lasso-Event | The event type (e.g., table.completed). |
X-Lasso-Delivery-Id | A unique identifier for this delivery attempt. |
X-Lasso-Signature | HMAC-SHA256 signature of the request body (if a secret is configured). |
Verifying signatures
If you provide a webhook secret, the API signs each payload using HMAC-SHA256. The signature is sent in theX-Lasso-Signature header with a sha256= prefix.
Retry policy
If your endpoint does not respond with a2xx status code within 10 seconds, the API retries with exponential backoff:
| Attempt | Delay |
|---|---|
| 1st retry | 30 seconds |
| 2nd retry | 5 minutes |
| 3rd retry | 30 minutes |
Catalog and attribute webhooks
For catalog products and attribute dictionary changes, subscribe via Catalog Webhooks. Supported events:| Event | Description |
|---|---|
product.created | A catalog product was created |
product.updated | A catalog product was updated |
product.deleted | A catalog product was deleted |
attribute.created | An attribute dictionary entry was created |
attribute.updated | An attribute was updated or renamed |
attribute.deleted | An attribute was deleted |
attribute_id and the full attribute object in data.
Custom auth headers
You can include a custom authentication header on webhook deliveries by settingwebhook_auth_header_name and webhook_auth_header_value in your table creation input data.
