For developers

Feature requests, as an API.

Drop in the widget and you're live in minutes. Or build requests, votes and comments into your own interface with the REST API. Either way, your users sign in with the login they already have.

<!-- One line, anywhere in your app -->
<script
  src="https://list79.com/widget.js"
  data-key="pk_your_public_key"
  data-user-token="{{ signedUserToken }}"
  async></script>
# Most-voted requests first
curl https://list79.com/api/v1/requests \
  -H "Authorization: Bearer sk_…"

{ "items": [ { "number": 12,
    "title": "Export to CSV",
    "status": "planned", "votes": 48 } ],
  "total": 1, "offset": 0, "limit": 50 }
# A customer asked on a call: add their vote
curl -X POST https://list79.com/api/v1/requests/12/votes \
  -H "Authorization: Bearer sk_…" \
  -H "Content-Type: application/json" \
  -d '{ "user": { "id": "u_8213",
        "email": "pat@example.com" } }'

{ "number": 12, "votes": 49, "voted": true }

Three ways in

Start with a script tag. Go fully headless when you're ready.

Drop-in widget

A "Suggest a feature" button and panel in your app. Search, vote and suggest without leaving your product. Drawn in its own shadow root, so your CSS and ours never clash.

REST API

Build the board into your own UI from the browser with @list79/client and React hooks, or work with requests from your server with a secret key: forward them from your support desk, add votes from your CRM.

Hosted portal

A public board and roadmap at list79.com/p/your-product, with your icon, screenshots and milestones. People sign in through your app, or with just their email.

Quickstart

Live in your app in four steps.

  1. Create a product

    Start a free trial and add your product. Its Keys page has your public key (pk_…), your widget secret, and secret API keys (sk_…). Switch to Test for pk_test_ and sk_test_ keys with their own data, for development and CI.

  2. Sign a user token on your server

    A short-lived JWT (HS256) signed with your widget secret: sub is your user ID, plus exp, and optionally email, name and locale. Works with any auth: your own, Clerk, Supabase, Firebase, Auth0. Keep the secret on the server.

  3. Add the widget

    Put the script tag on your pages with the token. Your users can vote and suggest straight away, with no second sign-up.

  4. Go headless if you like

    Call the REST API from your backend with a secret key to show requests in your own UI, or to bring in requests from anywhere.

// npm install jsonwebtoken
import jwt from "jsonwebtoken";

const token = jwt.sign(
  { sub: user.id, email: user.email, name: user.name },
  process.env.LIST79_WIDGET_SECRET,
  { algorithm: "HS256", expiresIn: "1h" });
// System.IdentityModel.Tokens.Jwt
var key = new SymmetricSecurityKey(
    Encoding.UTF8.GetBytes(widgetSecret));
var token = new JwtSecurityTokenHandler().WriteToken(
  new JwtSecurityToken(
    claims: [new("sub", user.Id), new("email", user.Email)],
    expires: DateTime.UtcNow.AddHours(1),
    signingCredentials: new SigningCredentials(
      key, SecurityAlgorithms.HmacSha256)));
# pip install pyjwt
import jwt, os, time

token = jwt.encode(
    {"sub": user.id, "email": user.email,
     "exp": int(time.time()) + 3600},
    os.environ["LIST79_WIDGET_SECRET"],
    algorithm="HS256")

REST API

Small, predictable, and documented.

Every call uses a product's secret key as a bearer token and only ever sees that product. Every endpoint, with examples in four languages and a Try it panel, is in the API reference; the OpenAPI document loads into Postman, Insomnia or your code generator. What's changed, and our promise not to break v1: changelog.

CallWhat it does
GET /api/v1/requestsList requests, most-voted first. Filter with status, sort with sort=newest or updated, page with offset and limit (up to 100).
GET /api/v1/requests/{number}One request. A merged request points to the one that now holds its votes.
POST /api/v1/requestsCreate a request for a user. Their vote is added.
POST /api/v1/requests/{number}/votesVote as a user. Voting twice is harmless.
DELETE /api/v1/requests/{number}/votes/{userId}Remove a user's vote.
GET /api/v1/requests/{number}/commentsPublic comments, oldest first.
POST /api/v1/requests/{number}/commentsComment as a user.
PUT /api/v1/users/{userId}Create or update a user's email, name and monthly revenue.
DELETE /api/v1/users/{userId}Delete a user's data when they delete their account in your app.
Your team's side
PATCH /api/v1/requests/{number}Change the status. Planned, shipped and declined email the people who asked.
POST /api/v1/requests/{number}/decisionsRecord a decision with its public reason (required to decline).
POST /api/v1/requests/{number}/mergeMerge a duplicate into another request; votes move, one per user.
POST /api/v1/requests/{number}/repliesReply publicly as the team.
GET POST /api/v1/requests/{number}/notesInternal notes, never shown to users.
GET /api/v1/requests/{number}/votersWho voted, with the monthly revenue you've sent.
GET POST /api/v1/requests/{number}/linksLink GitHub issues and pull requests; closing them ships the request.
GET POST PUT DELETE /api/v1/milestonesThe portal's roadmap: milestones and the requests each covers.
  • JSON with camelCase names; statuses are strings such as "underReview"
  • Errors in the standard problem details format, with each invalid field listed
  • 300 calls a minute per product, with RateLimit-Remaining and RateLimit-Reset on every answer; after that, 429 with Retry-After
  • Send an Idempotency-Key with any change and retry safely: the same key gets the same answer for 24 hours, never a duplicate
  • Every answer has a List79-Request-Id, which the request log shows too; read-only keys for dashboards
  • Users are your own user IDs, created the first time you use them
  • Changes made with a key are credited to it on the request page ("API key “CI”")
  • A request log on each product's Keys page: the last 7 days of calls and why any failed, plus a checker that explains any user token
  • Connect GitHub (Keys → GitHub) and a request ships when its linked issue closes as completed or its pull request merges

Your own UI

Headless, from the browser.

Build the feedback board into your app, your way. @list79/client calls List79 straight from the browser with your public key and the user's token, so your server only signs the token; it doesn't relay every call. React hooks handle loading, optimistic votes and refreshing.

  • Typed, no dependencies, works with React 18 and 19
  • Safe in the browser: a caller can only act as the user in the token
  • Requests, search, voting, suggesting and comments; the client API underneath
npm install @list79/client

@list79/client on npm →

import { List79Provider, useRequests, useVote }
  from "@list79/client/react";

function Board() {
  const { requests } = useRequests({ filter: "popular" });
  const vote = useVote();
  return requests.map(r => {
    const { votes, voted } = vote.display(r);
    return <button onClick={() => vote.toggle(r)}>
      ▲ {votes} {r.title}</button>;
  });
}

<List79Provider publicKey="pk_…" userToken={getToken}>
  <Board />
</List79Provider>
import { createClient } from "@list79/client";

const list79 = createClient({
  publicKey: "pk_…",
  userToken: () => fetch("/api/list79-token").then(r => r.text()),
});

const { items } = await list79.listRequests({ filter: "new" });
await list79.vote(items[0].number);
await list79.suggest({ title: "Export to CSV" });

Widget

Make it yours.

Attributes on the script tag set it up; four functions let your app drive it.

Widget guide →

data-keyYour product's public key. Required.
data-user-tokenThe token your server signs. Without it, people can browse but not vote.
data-launcher="false"Hide the floating button and open the panel from your own.
data-colorYour accent colour, e.g. #1a73e8. Without it, the widget uses the brand colour set under Portal look, else neutral black.
data-langen, ja, es, fr, de, zh or ko.
List79.open() / close()Show or hide the panel.
List79.setUserToken(token)After your user signs in or out.
List79.setLanguage(code)Follow your app's language.

Webhooks

Know the moment something happens.

Add an endpoint on your product's Webhooks page (under Keys) and List79 posts each event to it as JSON: post to Slack, update your CRM, or tell the customer who asked. Test mode has its own endpoints.

EventWhen
request.createdA request is created, from the widget, portal, API or your team.
request.status_changedIts status changes, with previousStatus and any public reason.
request.mergedIt's merged into another request as a duplicate.
vote.createdSomeone votes for it.
vote.deletedSomeone takes their vote back.
comment.createdSomeone, or your team, comments on it.
{
  "id": "evt_01a1…",
  "type": "request.status_changed",
  "createdAt": "2026-11-15T09:30:00Z",
  "livemode": true,
  "product": { "slug": "acme", "name": "Acme" },
  "data": {
    "request": { "number": 12, "title": "Export to CSV",
      "status": "shipped", "votes": 48, … },
    "previousStatus": "inProgress",
    "reason": null
  }
}
import crypto from "node:crypto";

// header: "t=1731663000,v1=5f2c…"; body: the raw request body
function verify(header, body, secret) {
  const { t, v1 } = Object.fromEntries(
    header.split(",").map(p => p.split("=")));
  const mac = crypto.createHmac("sha256", secret)
    .update(`${t}.${body}`).digest("hex");
  const fresh = Math.abs(Date.now() / 1000 - t) < 300;
  return fresh && crypto.timingSafeEqual(
    Buffer.from(mac), Buffer.from(v1));
}
  • Signed: the List79-Signature header is an HMAC-SHA256 of the timestamp and body with your endpoint's secret
  • Answer with any 2xx within 10 seconds; anything else is retried 7 more times over about a day
  • Every event has an ID (List79-Event-Id), the same on retries, so you can skip duplicates
  • A delivery log for each endpoint, with "Send test event" and "Send again"; switched off after 3 days of failures, with an email to you

AI tools

Ask Claude what your customers want.

List79 is an MCP server. Connect Claude, Cursor or any MCP client with a product's secret key and ask in plain words: "what do our paying customers want most?", "summarise the requests about exports", "mark #12 shipped and thank everyone".

  • Read: requests, search, voters with revenue, what paying customers want most, milestones
  • Act: change status, record a decision, add a note, reply, merge duplicates; credited to the key, with the same emails and webhooks as the app
  • A read-only key lets AI look without changing anything; a sk_test_ key keeps it in test mode
claude mcp add --transport http list79 \
  https://list79.com/mcp \
  --header "Authorization: Bearer sk_…"
{
  "mcpServers": {
    "list79": {
      "url": "https://list79.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_…"
      }
    }
  }
}

Good to know

Built to be trusted with your users.

Your login, not ours

Users are who your server says they are. Nobody can vote as someone else, and nobody signs up twice. The portal uses the same token, or email links if you'd rather not build anything.

Keys done properly

Secret keys are shown once and stored only as a hash. Each one works for one product, and you can revoke it at any time.

Delete means delete

When a user leaves your app, one DELETE call removes their profile, votes and comments. Emails are never shown on the portal.

Seven languages

The widget and portal speak English, Japanese, Spanish, French, German, Chinese and Korean, following your setting, the user's token, or their browser.

Test mode

Separate test keys with their own requests, users and portal. Build and run CI against them; nothing reaches your live board, and nobody gets emailed. Clear it with one click.

Any stack

No SDK to install. The widget is one script and the API is plain HTTPS and JSON, so it works from Rails, Laravel, Django, .NET, Node or a serverless function.

Ship it this afternoon.

14-day trial, no card needed. One script tag to start; the whole API when you need it.