Skip to content

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
Terminal
curl https://feedback.acme.com/api/v1/posts \
  -G -d sort=votes -d limit=2 \
  -H "Authorization: Bearer $QUACKBACK_API_KEY"
200 OK · application/json
{
  "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 overview

Feedback

Posts, votes, comments, boards, statuses, tags and roadmaps. Add a vote for a customer who asked on a call.

Changelog

Draft, publish or schedule entries from your release process, and link them to the requests they ship.

Help center

Write and publish articles and categories from the tools where your docs already live.

Conversations and tickets

Read threads, reply, add notes, assign and change status from your own systems.

Status page

Update components and open incidents straight from your monitoring tools.

Customers

Users and companies, so every request carries the context from your app. Segments are on Business and up.

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.

Terminal
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 guide
webhook.js
import 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))
  );
}
Scoped API keysRead, or read and write, for feedback, the help center, conversations and settings. Changelog access is write only.
Rotate and revokeRotate a key and the old one stops working straight away.
OpenAPI specGenerate a client from /api/v1/openapi/json on your workspace.
Cursor paginationUp to 100 results a page, with a cursor for the next.
One error shapeEvery error returns a status, a code and a readable message.
Set up the APICreate a scoped key and make your first request.
Set up webhooksPick the events, add your endpoint and verify the signature. On Pro and up.
Same on Cloud and self-hostedThe same API runs on our cloud and on your own servers.

Common 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.

Start building on Quackback