20 Oct 2026, 01:16 UTC · 1 question · ID 8ecbe3efc35a
Who asked
Profile
We don’t have a profile for this visitor.
Question 1
“What does the Hourglass-Signature header contain, and how do I check it?”
Answer
✕Not answered
The site never mentions webhooks, the API or a signature header. Nothing explains what the header contains or how to verify that a webhook came from Hourglass.
Who needs it: Developers and IT teams building integrations
What is missing
No guide covers the API, webhooks or verifying webhook signatures.
Where
Update this section: add a fifth card beside "Your first day", "Moving from your current CRM", "How agents work in Hourglass" and "Security and control".
What to do
Add a developer card listing webhooks, signature verification and the API as its points.
Link the card to the new webhooks section on /products/data.
Done when: /resources shows a developer guide card that links to webhook signature verification. Depends on: “Add a webhooks and API section to /products/data”
The page for IT and data teams mentions syncs but never webhooks, the API or how webhook calls are signed.
Where
Update this section: add a line on webhooks and signed events to the list under "Bring every source into one record", beside "Two-way syncs with the systems you run".
What to do
Add a line saying events can be sent by signed webhooks, as confirmed by engineering.
Link the line to the webhooks section on /products/data.
Done when: /platform mentions webhooks and links to how to verify their signatures. Depends on: “Add a webhooks and API section to /products/data”
Answer full page
The Hourglass-Signature header lets you confirm a webhook really came from Hourglass, and the docs section below explains what it holds and how to verify it. I don't have the exact header format here, so please follow the steps in the linked guide.