Set up HeedPost without guesswork.
Start with a public board, bring feedback into your product, or connect HeedPost to the tools you already use. Every example uses the real addresses and the real request shapes.
From workspace to first response.
Pick the part you are wiring up.
Three addresses, and what answers at each.
Knowing which host does what saves most of the questions people ask while wiring HeedPost up.
acme.heedpost.comyour workspaceThe board, the roadmap, the changelog and the sign-in, for customers and your team. On Plus and Pro it also answers on your own domain, like
feedback.yourcompany.com. The widget's script,/widget.js, is served from here, so it already knows your name and colour.api.heedpost.comevery workspaceThe REST API at
/v1/and the MCP server at/v1/mcp. One host for everyone: the key names the workspace, so there is no subdomain to configure.heedpost.comthis siteThe product's own pages, these docs and the help centre. Signing in happens on the workspace, not here.
Looking for how to do something in the app?
Merging, statuses, the changelog, your domain, plans and refunds are in the help centre, written as tasks. Open the help centre, or tell us what you're building.