Product deal feed API: on-sale affiliate SKUs, discounts, and images in one REST contract

Endpoints: account product deal feed and global catalogue

Customer product deal rows live under POST /api/v1/me/products. Cross-tenant discovery (no publisher offerUrl) uses POST /api/v1/catalog/products. Both are Bearer-token JSON, pageable, and documented in OpenAPI.

Try product deal list calls

Create an fdco_ token in the dashboard, then POST JSON. Interactive docs: api.feedico.io/api-docs. Use /me/products for your connected programmes (includes offerUrl when synced) and /catalog/products for cross-tenant discovery without shared tracking links.

curl -sS -X POST 'https://api.feedico.io/api/v1/me/products' \
  -H 'Authorization: Bearer fdco_YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"pageSize":50,"firmName":"Belk"}'

{
  "ok": true,
  "recordCount": 50,
  "page": 1,
  "pageSize": 50,
  "nextCursor": "4790020",
  "availableProviders": ["cj_affiliate"],
  "products": [
    {
      "id": "4790020",
      "networkId": "9204412",
      "firmName": "Example Merchant",
      "provider": "cj_affiliate",
      "externalProductId": "sku-123",
      "title": "Wireless earbuds on sale",
      "brand": "ExampleBrand",
      "price": 79.99,
      "salePrice": 49.99,
      "discountPercentage": 37.5,
      "currency": "USD",
      "offerUrl": "https://www.example.com/p/sku-123?sid=pub",
      "availability": "in stock",
      "fetchedAt": "2026-09-05T10:22:20.000Z",
      "status": "active",
      "images": [
        { "url": "https://cdn.example.com/p.jpg", "sortOrder": 0, "isPrimary": true }
      ]
    }
  ]
}

curl -sS -X POST 'https://api.feedico.io/api/v1/catalog/products' \
  -H 'Authorization: Bearer fdco_YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"pageSize":50,"q":"earbuds","minPrice":20,"maxPrice":80}'

curl -sS -X POST 'https://api.feedico.io/api/v1/catalog/products' \
  -H 'Authorization: Bearer fdco_YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"pageSize":100,"cursor":"PREVIOUS_nextCursor","provider":"cj_affiliate"}'

{
  "ok": true,
  "recordCount": 50,
  "page": 1,
  "pageSize": 50,
  "nextCursor": "catalog_a1b2c3d4e5f67890",
  "availableProviders": ["cj_affiliate"],
  "products": [
    {
      "id": "prod_9f8e7d6c5b4a3210",
      "firmName": "Example Merchant",
      "provider": "cj_affiliate",
      "title": "Wireless earbuds on sale",
      "brand": "ExampleBrand",
      "sku": "sku-123",
      "price": 79.99,
      "salePrice": 49.99,
      "discountPercentage": 37.5,
      "currency": "USD",
      "merchantUrl": "https://www.example.com",
      "fetchedAt": "2026-09-05T10:22:20.000Z",
      "images": [
        { "url": "https://cdn.example.com/p.jpg", "sortOrder": 0, "isPrimary": true }
      ]
    }
  ]
}

Pagination, filters, and warehouse pulls

Both product endpoints accept a JSON body. Start with { "pageSize": 100 }, then pass the previous nextCursor until it is null. Cap is 500 rows per call. Successful list calls count toward your plan quota (UTC month).

Product deal fields that power merchandising

Upstream networks disagree on field names. Feedico normalizes them into one ProductRow so your templates stay stable when you add programmes.

• Commercial

  price, salePrice, discountPercentage, sale windows, currency, availability

• Identity

  title, brand, sku, gtin, externalProductId, firmName, provider

• Creative

  images[] with url, sortOrder, isPrimary for cards and carousels

• Tracking

  offerUrl on /me only; catalog omits it so you attach your own links

How publishers wire the product deal feed

1. Connect programmes in the dashboard (CJ and peers your account is approved for).
2. Confirm plan entitlement for product feed on Pro or Business.
3. Page /me/products into your warehouse or CMS cache on a schedule; store nextCursor between runs.
4. Merchandize dealswith salePrice < price and discountPercentage in UI; keep coupon codes on a separate coupon API path.
5. Optional discovery via /catalog/products when you need brand/SKU search without another publisher's tracking URL.

Product deal feed vs coupon API vs deal feed

Networks behind the product deal feed

Connect approved programmes in the dashboard. Product deal catalogue sync currently highlights CJ Affiliate sale pulls; coupon and merchant normalization already spans the networks below. One Bearer token covers the surfaces your plan unlocks.

• 
  CJ Affiliate
• 
  Awin
• 
  Impact
• 
  Admitad
• 
  TradeTracker
• 
  Partnerize

Product deal feed API FAQ

What is a product deal feed API?

A product deal feed API returns SKU-level catalogue rows that are commercially actionable as deals: titles, brands, list price, sale price, discount percentage, images, availability, and merchant context as JSON over HTTPS. Feedico's product deal feed API normalizes on-sale affiliate catalogue rows into one listing contract for deal sites, price-drop widgets, and shopping assistants.

How is a product deal feed different from a deal feed API?

In affiliate tooling, deal feed API usually means coupon and promotion rows (codes, offer text, expiry). A product deal feed is different: it is a product catalogue filtered or enriched for deals (salePrice, discountPercentage) at the SKU level. Use Feedico's coupon API for codes; use the product deal feed API for discounted products.

Is this the same as a product feed API?

Yes at the contract level. Product feed API is the industry name for SKU catalogue endpoints. Product deal feed API is how we describe Feedico's sale-focused product catalogue: the same ProductRow shape, biased toward deal-relevant rows so publishers can merchandize discounts without ingesting every full-price SKU.

How is a product deal feed API different from a coupon API?

A coupon API returns promo codes, voucher titles, and eligibility windows. A product deal feed API returns individual products with pricing: SKU or GTIN, list vs sale price, discount %, and images. Many publishers run both: coupons for code-led pages and product deals for grids, carousels, and price-drop alerts.

Which endpoint do I call for my account product deal feed?

Authenticated tenants call POST /api/v1/me/products with a Bearer fdco_ token. Responses include images[], sale fields, firmName, provider, and cursor pagination. Filters include firmName, brand, sku, currency, price bounds, and free-text q.

What is the global catalogue products endpoint?

POST /api/v1/catalog/products returns discovery-oriented product rows from the aggregated index. Catalogue product responses omit publisher-specific offerUrl values so you attach your own compliant tracking links when publishing.

Does Feedico sync full catalogues or sale products only?

The live sync shown on this page focuses on on-sale catalogue rows from connected CJ Affiliate programmes (discount and sale-price filters) so the feed stays deal-relevant. Exact sync policy can evolve; confirm current behaviour in docs and your dashboard entitlements.

Which plan includes the product deal feed API?

Product feed access (including the product deal feed) is included on Pro and Business. Free and Starter include merchant and coupon data but not the product feed entitlement. See Pricing for caps and upgrade paths.

How often is the product deal feed refreshed?

Connected product catalogues refresh on a scheduled cadence (typically daily for full CJ product pulls) with manual sync available for operators. This landing page surfaces the last successful sync timestamp and a live sample of recently upserted sale products.

What fields are normalized on each product deal?

Typical fields include title, description, brand, sku, gtin, price, salePrice, sale windows, discountPercentage, currency, availability, merchant/firm identity, provider, fetchedAt, status, and images[]. Upstream networks use different shapes; Feedico maps them into one ProductRow contract.

When should I use /catalog/products instead of /me/products?

Use POST /api/v1/me/products when you need your connected programmes, including offerUrl when synced. Use POST /api/v1/catalog/products for cross-tenant discovery and brand/SKU search without another publisher's tracking links. Catalogue responses intentionally omit offerUrl.

Is this the same as /product/api?

No. /product/api is the Feedico product overview for the unified REST surface (merchants, coupons, and related developer tooling). /product-deal-feed-api is the SEO and documentation landing for the sale-focused SKU product deal feed and the /me/products and /catalog/products contracts.