Wedding Registry API: Prices, Stock and Store Choice for Every Item

Couples register at one store, but guests can buy a gift at several. This guide covers what wedding registry product data takes to build yourself, how Affiliate.com handles it, and how to handle a registered store that has run out, with a demo.

Affiliate.com Wedding Registry API: Prices, Stock and Store Choice for Every Item graphic

A wedding registry API gives a wedding registry the part that is hardest to build: the product data for every gift. One request returns what the gift is, every store that sells it, today’s price in each and whether it is in stock. Couples usually register at one store, but their guests are not tied to it. A guest may find the same blender cheaper elsewhere, or reach the registered store to find it sold out. This guide covers what that data takes to build yourself, how Affiliate.com handles it, and how a registry can use it to choose where a guest buys. The demo below uses prices last pulled November 16, 2026.

What it takes to build a wedding registry’s product data yourself

A wedding registry is open for months, and its gifts are considered ones: cookware, bedding, glassware. Guests buy over the whole engagement, so the data has to stay right without anyone editing the list. For every gift, you would have to keep five things correct.

What a wedding registry has to trackWhat it takes to build yourself
Which product the gift isA set, a size or a color is a different product from its lookalikes. You need a reliable way to match the same gift across stores.
Where else it is soldA connection to each retailer, so a guest who does not want the registered store has somewhere else to go.
What it costs todayA price from every store, refreshed often enough that a price saved at registration does not mislead a guest months later.
Whether a guest can buy itStock in each store, including the registered one, which is the store most likely to be the dead end.
How to buy itA working link to each store’s page, with the affiliate tracking that goes with it.

Keeping this current across many retailers for the length of an engagement is a data pipeline, not a registry feature.

How Affiliate.com handles it

Affiliate.com does the tracking. A registry sends the gift’s barcode and gets back every store with its price and stock, already matched and current.

The registry needsThe requestWhat comes back
To find a gift to addPOST /v1/products with a name searchMatching products with their barcodes, names, pictures and prices.
The same gift in every storeThe barcode in every requestThe product itself, whichever store sells it.
Every store, price and stock levelPOST /v1/products/price-history for the barcodeEach store that sells it, with price, regular price, stock and recent range, and a link to its page.
To add a gift from a pasted linkPOST /v1/tools/convert/url-to-barcodeThe barcode for the product on that page.

Our guide to barcode search covers the identifiers. The same requests are available as MCP tools, which MCP or REST explains.

Choose where guests buy each gift

The demo groups real products by room. Pick a room and a gift, then choose the store the couple registered at. The page shows every store with its price and stock. If the store you chose has the gift in stock, it says where guests are sent and whether another store has it for less. If it has run out, it shows the next best store. Every figure comes from one real Price History API response for that product’s barcode, and the page holds a set of products rebuilt every night.

Choose a store that shows as out of stock, where there is one. That is the case a registry built around a single store gets wrong, and the reason to keep every store from the response.

The store choice, step by step

StepWhat the registry does
1. AskSend the gift’s barcode to the price history endpoint and read every store in the response.
2. FilterKeep the stores that have the gift in stock today.
3. Prefer the couple’s storeIf the registered store is in that list, use it.
4. Fall backIf not, use the cheapest store in the list, and tell the guest the first choice has run out.
5. LinkSend the guest to the product link for the store you chose.

Whether to favor the registered store or the lowest price is a product decision. Some couples care where the gift comes from, for store credit or returns. Others only care that it arrives. The data supports either, so it can be a setting.

Couples who register at more than one store

Many couples register at two or three stores, which splits one wish list across several systems. For a guest that is more work, and for the couple it makes duplicates easy: the same gift can sit on two registries and be bought twice. Because the barcode is the same everywhere, a registry that keeps its list by barcode can show each gift once, with every store that sells it. Our Gift Registry API guide covers the same idea for any registry.

Rooms and timing

Wedding lists are usually grouped by room: kitchen, bedroom, dining and the rest of the house. A product’s category field is each merchant’s own text, so keep the room in your own data, saved with the barcode when the gift is added. Then every guest sees the same grouping.

Most purchases come in the weeks around the shower and the wedding. Check when the registry is shown, so a guest never sees stale data, and run a nightly check across the whole registry in the last two months, so the couple hears about a problem gift while there is time to swap it. Checking more often than daily rarely finds anything new, because the data behind the response changes over hours. How often product pages should be updated covers the schedule, and how price history helps a reader trust a deal shows how to back up a discount. Guests who want ideas first can use the Gift Guide API guide.

What the November 16, 2026 pull shows

On November 16, 2026 we pulled every store that sells each of the eight products in that day’s set. One of the eight products had at least one store that did not have them in stock. Four of the eight products with two or more stores in stock had a gap of at least ten percent between the cheapest and the most expensive store. For the first group a registry needs a fallback, and for the second it has a real choice to offer a guest.

ProductStoresIn stockCheapest in stockHighest in stockGap
Mikasa Samantha 16-piece dinnerware set44$78.40$164.99110%
Riedel Superleggero champagne glass33$75.00$75.000%
Tempur-Pedic Tempur-Cloud pillow44$84.00$84.000%
Northwest throw blanket54$40.00$59.9950%
Staub stoneware mini cocottes77$69.96$69.990%
Bissell TurboClean upright vacuum77$123.99$124.991%
Calphalon Premier 6-piece cookware set44$299.99$399.9933%
Calphalon Premier 15-piece knife set44$179.99$239.9933%

This table is fixed to November 16, 2026. The demo above is rebuilt every night from a rotating set of products, so its figures will change. Treat the table as a record of one day. Rooms are our own grouping for the demo and not a merchant category. Each figure is a store’s current price in US dollars, and the gap is the difference between the cheapest and the most expensive in-stock store, as a percentage of the cheapest.

Getting started in three steps

StepWhat to do
1. Get a keyRequest an API key from Affiliate.com. REST requests send it as a Bearer token in the Authorization header, and an MCP client uses the same key.
2. Save the barcode and the roomStore the barcode, the room and the store the couple registered at. Leave price and stock out of your database.
3. Choose the store when it is shownFetch the gift, keep the in-stock stores, prefer the registered one and fall back to the cheapest.
One API call
Store choice for every registry item
  • ✓Every store, price and stock level in one request
  • ✓A fallback when the registered store runs out
  • ✓The same data as an MCP tool or a REST request
Get API access →
Request
{
  "target_type": "barcode",
  "target_ids": [
    "885991222392"
  ],
  "currency": "USD",
  "include_series": false,
  "include_stats": true,
  "include_product": true,
  "per_page": 25
}