When the job changes, your systems know.
Proposal approved, invoice paid, job scheduled — SightLine fires a signed webhook the moment it happens, so your own services and no-code automations react in real time. No polling, no nightly export, no glue server to babysit.
Polling an API on a timer, hoping you did not miss it.
Event happens. Signed POST. Your endpoint. Retried if needed.
The moment a proposal is approved, an invoice is paid, or a job is scheduled, SightLine signs the payload and posts it straight to your endpoint — retrying if you are down.
The moments that matter, as events.
A customer signs off.
Fires the instant a customer approves a proposal — react before the ink dries.
Payment lands.
Fires the moment an invoice is paid, so your books and downstream systems update immediately.
A job hits the calendar.
Fires when a job is booked, so dispatch, staffing, or a calendar sync can react right away.
A takeoff is captured.
Fires when a measurement is added to a job, so downstream estimating or ordering tools stay current.
Film leaves the shelf.
Fires when a roll is reserved or checked out, so inventory systems reflect the change immediately.
Wire it without a server.
Point a webhook at a no-code automation tool and react to any event without writing a line of code.
Signed, delivered, retried.
Webhooks, answered.
How do I verify a webhook actually came from SightLine?
Every payload includes an X-SightLine-Signature header — a signature computed over the timestamp and body. Recompute it with your endpoint secret and compare before you trust the event.
What happens if my endpoint is down?
If your endpoint does not respond with a 2xx status, SightLine retries the delivery, so a temporary outage on your end does not cost you the event.
Which events can I subscribe to?
proposal.approved, invoice.paid, job.scheduled, measurement.added, and roll.checked_out today, with more event types on the roadmap.
Do I need to run a server to use webhooks?
No. Point a webhook at your own endpoint, or wire it into a no-code automation tool without writing any code.
How is this different from the API?
The API is for reading and writing the record on demand. Webhooks push you a signed event the instant something changes — use either on its own or both together.
Point a webhook and go.
Subscribe to the events you care about, verify the signature, and act. Full catalog and examples in the developer docs.
Book a demo