API and webhooks
Build on your support and feedback with a REST API
Read and write posts, votes, the changelog, help center articles, conversations and tickets. Signed webhooks tell your systems the moment something changes.
Start building today
- REST API on every plan, webhooks and MCP on Pro and above
- 14-day trial, no card needed
- Open source. Self-host with every feature
curl https://feedback.acme.com/api/v1/posts \
-G -d sort=votes -d limit=2 \
-H "Authorization: Bearer $QUACKBACK_API_KEY"{
"id": "3f2b8c1e-6d4a-4e2b-9a57-0c1d2e3f4a5b",
"type": "post.status_changed",
"createdAt": "2026-10-06T09:14:00.000Z",
"data": {
"post": {
"id": "post_01h455vb4pex5vsknk084sn02q",
"title": "Recurring invoices",
"boardSlug": "feature-requests"
},
"previousStatus": "Planned",
"newStatus": "In Progress"
}
}{
"data": [
{
"id": "post_01h455vb4pex5vsknk084sn02q",
"title": "Recurring invoices",
"voteCount": 323,
"boardSlug": "feature-requests"
},
{
"id": "post_01h455vb4pex5vsknk084sn02r",
"title": "Multi-currency support",
"voteCount": 298,
"boardSlug": "feature-requests"
}
],
"meta": {
"pagination": {
"cursor": "eyJvZmZzZXQiOjJ9",
"hasMore": true
}
}
}One API for your whole workspace
Everything your team does in Quackback, your code can do too. Each workspace serves its own interactive reference at /api/v1/docs.
Read the API overviewFeedback
Changelog
Help center
Conversations and tickets
Status page
Customers
Webhooks for everything that changes
Skip the polling. Quackback sends a signed request to your endpoint whenever a post, comment, changelog entry, conversation or ticket changes.
Subscribe to the events you need
Create a webhook in Settings or over the API. Pick events across feedback, support and the changelog, and limit post events to the boards you care about.
curl -X POST https://feedback.acme.com/api/v1/webhooks \
-H "Authorization: Bearer $QUACKBACK_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://api.acme.com/hooks/quackback",
"events": ["post.created", "post.status_changed"]
}'Verify every delivery
Each request carries an HMAC-SHA256 signature and a timestamp. Check both, respond quickly, and failed deliveries are retried over several hours.
Read the webhooks guideimport crypto from "node:crypto";
// Signed over "{timestamp}.{raw body}" with your webhook secret
export function isValid(rawBody, headers, secret) {
const timestamp = headers["x-quackback-timestamp"];
// Reject deliveries more than 5 minutes old
if (Math.abs(Date.now() / 1000 - Number(timestamp)) > 300) return false;
const expected =
"sha256=" +
crypto
.createHmac("sha256", secret)
.update(`${timestamp}.${rawBody}`)
.digest("hex");
const signature = headers["x-quackback-signature"] ?? "";
return (
signature.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected))
);
}Built the way you'd expect
Working with AI agents? Explore the MCP serverCommon questions
Which plans include the API and webhooks?
On Quackback Cloud, the REST API is included on every plan, including Free, and webhooks and the MCP server are included from Pro, each paid plan with a 14-day free trial. Rate limits rise with the plan, from 60 requests a minute on Free and Pro to 1,200 on Enterprise. The open-source, self-hosted edition includes all of them at no cost.
How do I authenticate with the Quackback API?
Create an API key in Settings, under Developers, and send it as a Bearer token in the Authorization header. Keys start with qb_, are shown once, and carry only the access you give them.
Is there an OpenAPI spec?
Yes. Browse the public reference at https://feedback.quackback.io/api/v1/docs. Every workspace also serves its own interactive reference at /api/v1/docs and the OpenAPI spec at /api/v1/openapi/json, matching the version you run, so you can generate a client in any language.
What are the API rate limits?
Requests are limited per minute. Self-hosted installs allow 100 requests a minute by default, and on Quackback Cloud the limit depends on your plan. Over the limit, you get a 429 response with a Retry-After header.
Should I poll the API or use webhooks?
Use webhooks for anything that should happen when something changes. Quackback sends a signed request as soon as a post, comment, conversation or ticket changes, so there's nothing to poll.
Have another question? Talk to the team.