Automation
Subscribe your own endpoint to cost events, verify each delivery by HMAC signature, and re-send failures.
Webhook events send Lineman cost events to an HTTPS endpoint you own, so your own systems can act on a budget breach when it fires. Every request carries an HMAC-SHA256 signature and a stable event id, so your receiver can check the request came from Lineman and ignore an id it has already handled. A 5xx, 408, 429 or network error is retried with backoff, and any other 4xx is given up on straight away. Every attempt is recorded with the status code and a bounded snippet of your endpoint's reply, and a recorded delivery can be re-sent once the receiver is fixed. Adding and managing an endpoint needs a company administrator.
Subscribe an endpoint to cost_alert.budget_day and cost_alert.budget_month, and each breach is posted to your https URL as JSON. Leave the event-type list empty and the same endpoint also receives types published later. Only a company administrator can add an endpoint, because it receives the whole company's cost events.
Every event carries an id, and a retry or a replay sends the original body again with that same id rather than minting a new one. One event delivered to two of your endpoints is still one id, not two. Key your own store on the id and each event is written once.
Every attempt is recorded in the delivery log with the status code and a bounded snippet of your endpoint's reply, so a broken receiver is visible rather than silent. Retries cover a 5xx, a 408, a 429 or a network error; any other 4xx is given up on straight away. Fix the receiver, then replay a recorded delivery.
The documentation walks through connecting it, what Lineman reads and writes, and the settings worth knowing about.
Read the setup guideEvery integration in one place, searchable by name and filterable by what it does.
View all integrations