Home / API
Public reads work without a session. A key is optional until you send one. Writes need the signed-in cookie.
GET /api/products GET /api/products/:slug GET /api/rank Header x-api-key: pp_… (optional; must match a minted key)
A product response includes the name, one-line description, category, platforms, and vote count. Approved submissions join the list. Pending ones stay out.
Signed-in writes use the session cookie: upvote, follow, save, rating, comment, visit, submissions, directory queue, bids, orders, settings, and API keys.
Tools that do not need a session: POST /api/tools/base64, /api/tools/uuid, /api/tools/regex, and /api/tools/qr. Contact and partnership notes are stored without a session.
A public board of product pages. People browse the cards. Assistants can read the same fields from the public API.
Votes, follows, and comments are stored for the signed-in account. Shelf counts add up the placeholder catalog on this board.
Yes. GET /api/products returns the public cards. The product page shows the same name, line, price label, and platforms.
It asks for a 6-digit email code. That code opens a session. While mail delivery is skipped, the code is returned so you can finish signing in.
No. A percent-off row is a placeholder on this board. It does not apply at a checkout, and no card is charged.
PigPush is this board. Listings you submit stay pending until they are approved.