Skip to main content

Concepts

Product​

A listing you own. It has a name, a title, a logo, a public URL, a subcategory, and a description. Those text fields, the logo, and the URL are read from the page and you can edit them. Dealpuffin keeps the final public address after redirects. Private and localhost addresses are refused. The public URL is https. Other people can see a listing that is not hidden once the URL is https — ownership verification is optional. If your verified email domain matches the host, or a DNS TXT record or /.well-known/dealpuffin-verification file shows you control it, the listing gets a Verified tag. Subcategories sit under a category, such as Error monitoring under Engineering. A product that fits nowhere else uses Other software. One account can publish many products.

Coupon​

The discount definition from the billing provider on that product: percent off or a fixed amount, and a duration of once, repeating for a number of months, or forever. Supported coupon providers are Stripe, Paddle, Polar, Lemon Squeezy, Dodo Payments, and RevenueCat (Web Billing). A coupon is not itself the thing a customer types.

Promotion code​

The customer-facing string attached to a coupon. This is what someone pastes at checkout. A coupon can have several promotion codes. Each code has its own active flag, expiry, customer lock, and redemption count. Dealpuffin keeps those as an internal pool under the coupon.

Offer​

A published coupon that still has at least one eligible promotion code. Browsers see the discount terms and a masked code. The public offer id is the coupon id. The code string is not in the page, and public search does not return it.

Claim​

The click, or the agent call, that reveals a code for an offer. One account can claim a given coupon once. The first reveal picks among currently eligible promotion codes (round-robin). Revealing again returns the same assigned code and does not count a second time.

Provider cap and Dealpuffin cap​

The billing provider's redemption cap is enforced at its checkout. A Dealpuffin cap, when one is set, can only be stricter. It limits how many people can reveal the code here. A code that leaks can still be used at that checkout after the Dealpuffin cap is full. Both limits are labeled so a seeker can tell them apart.

Proof point​

A figure read from a provider and shown on the listing. MRR from Stripe, Paddle, Polar, RevenueCat, Lemon Squeezy, or Dodo Payments; uptime from Better Stack, CloudWatch, or Google Cloud Monitoring; and traffic from Google Analytics. You choose the exact value, a band, or do not show, and the order. A band does not include the number in what seekers and agents receive. Do not show keeps the field connected but omits it from the listing. The catalog card shows the first three. The product page shows each one with the provider logo, the last sync, the cadence, and the trend. See Proof points.

Wish​

A request for a coupon that is not listed yet. It can sit on a product, or it can be an open wish in a category. A provider answers by publishing a real coupon, not by inventing a code on Dealpuffin.

An agent reads the open wishes with list_wishes and a category slug. A parent category includes its subcategories. The same tool with mine: true reads wishes filed on products that signed-in account submitted. See Wishes.

Agent key​

A Dealpuffin API key, or an OAuth connection, that lets an agent act as you. It is not a Stripe key. Each key only has the tools you turned on.