Your tools stay in step
Your CRM, warehouse and in-app banners update the moment something changes, without anyone copying it over.
Private previewWorkspaces are by invitation
Skip to content01Collect
Feedback boardsBoards that ask for exactly what your team needs to act.Votes, comments & mentionsOne vote per person, threads with mentions, and notes only your team sees.In-app widgetFeedback from inside your product, from customers who are already signed in.02Understand
Merge & duplicatesTen posts asking for the same thing become one, with every vote kept.User segments & revenueProSee which requests your biggest customers want, in dollars.InsightsWho reads, what's rising, and whether you answered.HeedPost AIPlus and ProTags, duplicate judging, drafts, summaries, themes and Ask, each with its own switch.03Ship and tell
Roadmap & statusesMove a post and everyone who asked hears, in your own status words.ChangelogRelease notes linked to the requests behind them, mailed to everyone who asked.Notifications & digestThe right email to the right person, and a switch for every one.04Run it
Activity logEvery change, who made it and when, a day at a time.Team, roles & sign-inUnlimited teammates, clear roles, and sign-in your way.Branding, domain & languagesYour logo and colour, your own domain, and 21 languages.ImportMove in from Canny, Featurebase or UserJot, with nobody emailed.05Connect
Slack & issue trackersPlus and ProSlack threads, and issues in Linear, Jira, GitHub or ClickUp that move posts back.MCP serverPlus and ProYour AI agent can read, file, vote and ship, as you.REST APIPlus and Pro27 operations and one key: build anything on top of your feedback.WebhooksPlus and Pro110 events, signed and retried, the moment they happen.Chapter 5 · Connect · Webhooks
A webhook is HeedPost calling your server the moment something happens: a vote, a status move, a release. Choose the events you want, verify the signature, and act on it in a few lines.
Try it
Press an action on the left and see exactly what your server receives.
On the right is what your server receives: the envelope, the headers and the signature header. Only the digest is a stand-in here, since the real one is made with your endpoint's secret.
vote.added, which you name.Pick an event to see what its data carries.
vote.added never names the voterStep by step
Give us your URL and choose the events it wants.
It's shown once, when you create or rotate the endpoint.
Check the signature against the raw body, and check the timestamp too.
Reply with a 2xx within 10 seconds, and do slow work afterwards.
A retried delivery carries the same event id, so you can skip one you've already handled.
Who it's for
Your CRM, warehouse and in-app banners update the moment something changes, without anyone copying it over.
Each new vote carries the new total, so a big request reaching fifty can page whoever's on call, with a few lines of code.
Every delivery is signed, so you know it came from us. Each event has an id. Keep track of it, and a retry never adds a second copy.
The details
Instead of your system asking HeedPost "anything new?" every few minutes, HeedPost tells it the moment something happens. Your developers give us an address, and we send each event there.
Pick the events an endpoint wants, or leave the list empty to get everything except votes, which you ask for by name because there are so many of them.
Every delivery is signed, so your server knows it came from HeedPost. It's retried if your server has a bad minute, and logged, so you can see what happened and send any delivery again.
No email address ever leaves in a webhook, and a vote never names the voter.
The API, the events, and what you can rely on when you build on it.
Each delivery carries X-Heedpost-Signature, X-Heedpost-Event and User-Agent: Heedpost-Webhooks/1. A redelivered event keeps its id, so you can skip one you've already handled.
{ "id", "type", "created_at", "workspace": { "id", "slug" },
"actor": { "id", "name" } | null, "subject": { "type", "id" }, "data": { … } }The signature header reads ts=<unix>;h1=<hex>, where h1 is an HMAC-SHA256 of <ts>:<raw body> using your endpoint's secret. Check it against the raw bytes, and check that the timestamp is recent. The secret is shown only when you create or rotate the endpoint.
Each attempt waits up to 10 seconds. A 5xx, a timeout or an address that doesn't resolve is retried, eight attempts in all, each wait twice as long as the last. A 4xx is your server's answer, so it isn't repeated. Redirects aren't followed.
An address inside a private network is turned down when you save it, and again when we send. We connect only to the addresses we checked, so a later DNS change can't point us somewhere private.
Each of these is a REST endpoint and, with the same name, an MCP tool.
GET/v1/webhookslist_webhooks Every endpoint this workspace sends events to, and how its recent deliveries went.POST/v1/webhooksadd_webhook Add an endpoint. The events you choose are sent to its URL, signed with a secret.PUT/v1/webhooks/{endpoint_id}edit_webhook Change an endpoint's URL or the events it wants. Send the whole set each time: a field you leave out is cleared, not kept.POST/v1/webhooks/{endpoint_id}/rotaterotate_webhook Get a new signing secret. It's shown in this answer only, and the old one stops working at once.DELETE/v1/webhooks/{endpoint_id}remove_webhook Unlike everything else on this API, removing an endpoint is permanent.All 110 types are listed, with what each one's data carries, in the catalog above.
Plans
Free is $0, Plus $29 and Pro $59 a month, per workspace. Never per seat. Every plan, line by line
| Feature | Free | Plus | Pro |
|---|---|---|---|
| Webhook endpoints | 0 | 1 (shared with Slack and trackers) | Unlimited |
| All 110 event types | Not included | Included | Included |
| Delivery log and resend | Not included | Included | Included |
Something else? Write to us, and a person answers.
Retries cover a bad few minutes. After that, the delivery waits in the log for you to send it again.
Yes. Choose any of the 110 per endpoint.
Check the X-Heedpost-Signature header with your secret, against the raw body.
An empty list means every type except vote.added, which you name to receive.
Rotate it. The new one is shown once, and the old one stops working at once.
Yes. Every attempt is logged with its status and time, and can be sent again.