Private previewWorkspaces are by invitation

HeedPost

01Collect

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

Collect

Understand

Ship and tell

Run it

Connect

Request an inviteSign in

Chapter 5 · Connect · REST API

27 operations, one key. Build anything on top of your feedback.

Your own software can read and write HeedPost through a plain JSON API. Put the roadmap on your site, file requests from your help desk, rank them by revenue, or copy everything into your warehouse. Press Send on any endpoint below.

Plan Plus and Pro. API keys are unlimited. 1,000 requests an hour per person.
GET /v1/posts"title":"votes":"status":"board":200 OK · 1 of 927 operations, one key
27operations, described by an OpenAPI document
3 kindsof key: read-only, read and write, MCP
1,000requests an hour, counted per person
Sentencesfor errors, never bare codes

Try it

Press Send.

Pick an endpoint, switch language, and send. Responses use the API's real field names.

GET/v1/posts


        
Responsepress Send

        

What teams build with it

Six jobs a key does on its first day. Each line is the call that does it.

Put the roadmap on your own site

Draw your planned and in-progress work in your own pages and style. A read-only key on your server can't change a thing.

GET /v1/posts?roadmap=true&kind=planned

File what support and sales hear

A button in your help desk or CRM files the request under the name of whoever's key it holds, with your custom fields filled in.

POST /v1/posts

Rank requests by revenue

Ask only for posts backed by customers worth $10k or more (the value is in cents). Team keys on Pro, because what a customer is worth never leaves the team.

GET /v1/posts?value_min=1000000&sort=votes

Mirror it into your warehouse

Page through every post in a stable order. Every list says how many rows match, so the loop knows when it's done.

GET /v1/posts?sort=oldest&limit=100&offset=200

Onboard a whole team in one script

Invite a list of addresses as members or admins. Unlimited team members on every plan, so invite everyone.

POST /v1/members

Ship from your release pipeline

When CI deploys, move the post to Shipped with a note. The note lands on the thread and every follower gets the email.

POST /v1/posts/{id}/status
3 kindsof key: read-only, read and write, and MCP. Hand each job the narrowest one.
1,000requests an hour, counted per person rather than per key or address
Sentencesfor errors: every refusal says what went wrong and, for a plan, which tier reaches it
No silent emptiesa misspelt status or board is a 404 or 422, never an empty list a sync job trusts

Step by step

How it fits into your week.

  1. Make a key

    Choose read-only, read and write, or MCP.

  2. Call an endpoint

    Send JSON with the key as a bearer token, and get JSON back.

  3. Page through lists

    Use limit and offset. The total tells you how many pages to expect.

  4. Handle errors

    Read the sentence in the detail field, and on a 429 wait as long as Retry-After asks.

  5. React to changes

    Use webhooks instead of asking again and again.

Who it's for

Three people, an ordinary week.

For PMs

Feedback in your own tools

Your help desk, CRM or dashboard can show and file feedback without anyone switching apps. Put the roadmap on your own website, in your own style.

For founders

No lock-in

Everything that matters is a request away. Support files a customer's request from the help desk, with your custom fields filled in.

For engineers

Predictable to build on

JSON in and out, pages in a stable order with a total, and a misspelt filter is an error, never an empty answer. Copy every post to your warehouse each night.

The details

Everything it does, explained.

What an API is

A way for software you already use to talk to HeedPost directly: read the board, file a post, move a status, invite people. Your developers write a few lines once, and it runs on its own.

Keys for each job

Make a key on Settings · Developers and choose what it may do: read only, read and write, or MCP for an AI agent. Give each job the narrowest key. Keys act as the person who made them.

Six things teams build first

  • The roadmap on their own website.
  • A "Send to HeedPost" button in their help desk or CRM.
  • A board ranked by the revenue behind each request.
  • A nightly copy into their data warehouse.
  • Onboarding a whole team from a list.
  • Marking work shipped from the release pipeline.

For developers.

The API, the events, and what you can rely on when you build on it.

Basics

The base URL is https://api.heedpost.com/v1. Send Authorization: Bearer <key> and JSON, and you get JSON back. The OpenAPI document at /v1/openapi.json needs no key, so you can generate a client from it. The reference on this site is drawn from the same document.

Errors

Every error is JSON with a sentence in detail. 400 means the request couldn't be read, and 401 a missing or revoked key. 402 means your plan doesn't include the feature, and the sentence names the plan that does. 403 means the wrong role or the wrong kind of key, 404 that nothing was found, 409 that the current state doesn't allow it, and 422 the wrong shape. 429 means too many requests, and comes with Retry-After.

Lists

Lists take limit and offset, and return a page whose total counts every match, not just this page. Every list has a stable order, so paging never shows an item twice or skips one.

Limits

Limits are counted per hour for the person the key acts as, not per address. Each person gets 1,000 requests, plus limits on posts, comments, votes, invitations and status moves that match what someone could do in a browser.

REST API and MCP tools

Each of these is a REST endpoint and, with the same name, an MCP tool.

  • POST/v1/posts/{post_id}/commentsadd_comment Reply on a post, as the person the key belongs to.
  • POST/v1/webhooksadd_webhook Add an endpoint. The events you choose are sent to its URL, signed with a secret.
  • POST/v1/boardscreate_board Make a board. The slug is its address, and every link to the board is built from it.
  • POST/v1/postscreate_post File a post, as the person the key belongs to.
  • DELETE/v1/boards/{slug}delete_board Deleting a board hides it and its posts. Nothing is destroyed, and you can bring it back from Settings, under Deleted.
  • PATCH/v1/boards/{slug}edit_board Change a board's name, description, visibility and switches. Its address has an endpoint of its own.
  • 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.
  • GET/v1/posts/{post_id}get_post One post in full, with its board, status, author, tags and demand.
  • POST/v1/membersinvite_member Invite someone by email. The answer is the pending invitation, without its link, which goes only to their inbox.
  • GET/v1/boardslist_boards Every board this key can see, in the workspace's own order.
  • GET/v1/posts/{post_id}/commentslist_comments Oldest first, in one flat list. A comment written while you page through is added at the end, so the pages you haven't read yet don't shift.
  • GET/v1/memberslist_members Everyone in this workspace, newest first.
  • GET/v1/postslist_posts Posts on this workspace's boards, newest first unless you choose another sort. Filter by board, status, kind or free text.
  • GET/v1/statuseslist_statuses Every current status, and the stage each belongs to. Read this first, so your client only sends ?status= names that exist.
  • GET/v1/tagslist_tags Every current tag in the workspace, in alphabetical order.
  • GET/v1/user-segmentslist_user_segments Every user segment, largest first. Team keys only.
  • GET/v1/webhookslist_webhooks Every endpoint this workspace sends events to, and how its recent deliveries went.
  • DELETE/v1/members/{user_id}remove_member Take someone off this workspace. Their posts, votes and comments stay, because those belong to them, not to their place on the team.
  • DELETE/v1/webhooks/{endpoint_id}remove_webhook Unlike everything else on this API, removing an endpoint is permanent.
  • 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.
  • PUT/v1/boards/{slug}/addressset_board_address Give a board a new address. Every address it has had keeps working, so a link someone sent last year still opens the board.
  • PATCH/v1/members/{user_id}set_member_role Make someone an admin, or make an admin a member again. The last admin can't step down, and gets a 409. Promote someone else first.
  • POST/v1/posts/{post_id}/statusset_post_status Give a post one of the workspace's statuses, by name. Only admins can do this. A move to a new stage emails everyone who follows the post.
  • DELETE/v1/posts/{post_id}/comments/{comment_id}/voteunvote_comment Take a comment vote back. It's safe to repeat. Voting on a comment doesn't follow anything, so there's nothing to unfollow.
  • DELETE/v1/posts/{post_id}/voteunvote_post Take a vote back. It's safe to repeat.
  • POST/v1/posts/{post_id}/comments/{comment_id}/votevote_comment Add a vote to a comment, as the person the key belongs to. Voting twice still counts as one vote.
  • POST/v1/posts/{post_id}/votevote_post Safe to repeat: voting twice still counts as one vote and sends one event.

Plans

What each plan includes.

Free is $0, Plus $29 and Pro $59 a month, per workspace. Never per seat. Every plan, line by line

FeatureFreePlusPro
REST APINot includedIncludedIncluded
API keys0UnlimitedUnlimited
Revenue filters and demandNot includedNot includedIncluded
Requests
1,000 an hour per person, reads included
Posts
10 an hour
Comments
100 an hour
Votes
120 an hour
Invitations
50 an hour
Status moves
120 an hour

What people ask us.

Something else? Write to us, and a person answers.

Is there an SDK?

You can generate one in your own language from /v1/openapi.json.

Can a key outlive the person who made it?

No. A key acts as its person. Remove them and the key stops working.

Are reads rate limited too?

Yes. Every request counts toward the 1,000 an hour.

Is there a sandbox?

Use a separate workspace. Keys only ever reach their own workspace.

Can I tell which plan an error is about?

Yes. The sentence in a 402 names the plan that includes it.

Are webhooks part of the API?

You manage webhook endpoints through the API, and deliveries arrive at your server.

Start hearing everyone.

Free for your first two boards, with no card.