Request format: method, headers and timeouts
Technical details of every Empath webhook request: method, headers, content type, timeout and what counts as success.
Technical details of the HTTP request Empath sends.
What does each request look like?
- Method —
POST - Body — JSON, UTF-8,
Content-Type: application/json(Slack format: see “Send webhook events to Slack”) - Timeout — 10 seconds
- Success — Any 2xx status. Everything else fails: other statuses, timeouts, TLS errors and redirects (3xx).
Headers
X-Empath-Event— The event type, same as the JSONtypeX-Empath-Delivery— The delivery ID, same as the JSONid. De-duplicate on this.X-Empath-Timestamp— Unix time in seconds when Empath signed the requestX-Empath-Signature—sha256=followed by the hex HMAC. See “Verify the signature”.- your custom header — If you set one. See “Create a webhook: the Endpoint step”.
Good to know
- Answer 2xx straight away and do your PSA or HR work afterwards, on a queue. Slow successes are fine; timeouts and errors use up Empath's retries. See “Retries, ordering and duplicates”.
Still need help?
Reach out to your Partner Success Manager, or email us at support@empathmsp.com. We’re happy to help!
Related articles
- Payload reference
- Verify the signature
- Retries, ordering and duplicates