Integrations · Automation and code
Signed webhooks for every change in Quackback
Pick the events, point them at an HTTPS endpoint, and get a signed JSON payload each time a post, comment, changelog entry, conversation or ticket changes.
Start collecting feedback today
- Included on Pro and above
- 14-day trial, no card needed
- Open source. Self-host with every feature
Quackback to your endpoint
- Post, vote, comment, changelog, conversation and ticket events
- SLA warnings, CSAT ratings and AI handoffs
- Signed with HMAC-SHA256 and retried when your endpoint fails
What you can do with webhooks
Explore the API and webhooksSet up webhooks
Read the step-by-step guideCreate a webhook
In Settings, open Developers, then Webhooks, and add an HTTPS endpoint.
Pick events
Choose the events to receive, and the boards for post events.
Verify signatures
Copy the signing secret and check X-Quackback-Signature on each request.
Common questions
How are webhook payloads signed?
With HMAC-SHA256 over the delivery timestamp and the raw body, using your webhook's signing secret. The signature arrives in the X-Quackback-Signature header and the timestamp in X-Quackback-Timestamp.
What happens if my endpoint is down?
Server errors, rate limits and timeouts are retried several times over a few hours. Other 4xx responses aren't retried, since sending the same request again wouldn't help.
Which events can a webhook receive?
Posts created, updated, voted on, merged, deleted or moved to a new status, plus comments and published changelog entries. On the support side: conversations, messages and tickets, CSAT ratings, AI handoffs, and SLA events when a target is close to breaching or has been missed.
Which plans include webhooks?
On Quackback Cloud, you get webhooks on the Pro, Business and Enterprise plans, with a 14-day free trial and no card needed. The open-source, self-hosted edition includes it at no cost.
Have another question? Talk to the team.