Product Data API: affiliate product catalogue for SKUs, prices, and images

When to use Product Data API vs Product Deal Feed

Both surfaces share the same underlying endpoints (/me/products, /catalog/products). The marketing pages differ by buyer intent: catalogue vs deal merchandising.

Endpoints table

Auth is Bearer token. Monthly API caps apply per plan. Related merchant parents: Merchant Data API.

Curl and JSON examples

curl -sS -X POST "https://api.feedico.io/api/v1/me/products" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"page":1,"pageSize":50,"provider":"cj_affiliate"}'

{
  "ok": true,
  "recordCount": 1,
  "page": 1,
  "pageSize": 50,
  "nextCursor": "4790020",
  "products": [
    {
      "id": "4790020",
      "provider": "cj_affiliate",
      "firmName": "Example Outdoor Co",
      "externalProductId": "SKU-ROPE-30",
      "title": "30m climbing rope",
      "brand": "ExampleBrand",
      "sku": "SKU-ROPE-30",
      "price": 129.0,
      "salePrice": 99.0,
      "discountPercentage": 23.3,
      "currency": "USD",
      "availability": "in stock",
      "offerUrl": "https://www.example-outdoor.com/p/rope-30?sid=pub",
      "images": [
        { "url": "https://cdn.example.com/rope.jpg", "sortOrder": 0, "isPrimary": true }
      ],
      "status": "active",
      "fetchedAt": "2026-09-07T10:22:20.000Z"
    }
  ],
  "availableProviders": ["cj_affiliate"]
}

curl -sS -X POST "https://api.feedico.io/api/v1/catalog/products" \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"page":1,"pageSize":50,"q":"rope"}'

{
  "ok": true,
  "recordCount": 1,
  "page": 1,
  "pageSize": 50,
  "nextCursor": "catalog_a1b2c3d4e5f67890",
  "products": [
    {
      "id": "prod_9f8e7d6c5b4a3210",
      "firmName": "Example Outdoor Co",
      "provider": "cj_affiliate",
      "title": "30m climbing rope",
      "brand": "ExampleBrand",
      "sku": "SKU-ROPE-30",
      "price": 129.0,
      "salePrice": 99.0,
      "currency": "USD",
      "availability": "in stock",
      "merchantUrl": "https://www.example-outdoor.com",
      "images": [
        { "url": "https://cdn.example.com/rope.jpg", "sortOrder": 0, "isPrimary": true }
      ],
      "fetchedAt": "2026-09-07T10:22:20.000Z"
    }
  ],
  "availableProviders": ["cj_affiliate"]
}

Field glossary

Architecture workflow

1. Confirm product feed entitlement on Pro or Business.
2. Connect programmes, then page /me/products into your warehouse using nextCursor.
3. Upsert on (provider, externalProductId) or sku within your tenant.
4. Render cards from title, brand, price/salePrice, images[]; route clicks through offerUrl when present.
5. For sale-only merchandising templates, lean on product deal feed copy and filters instead of re-inventing discount UI here.

Upstream product feeds
        |
        v
  Product rows  (/me/products)  + offerUrl when available
        |
        +-- Warehouse / search index (full catalogue)
        +-- Merchandising UI (optional salePrice filter)
        |
  Catalog discovery: /catalog/products (no offerUrl)

Related object APIs

• Merchant Data API

  Firm parents: displayName, provider, externalMerchantKey

• Offer Data API

  Coded coupons and title-only / auto-applied offers

• Commerce Data API

  Hub that ties merchant + product + offer together

• Unified affiliate API

  Product positioning across all Feedico list surfaces

Product Data API FAQ

What is the Product Data API?

It is Feedico's affiliate product catalogue API: SKU-level rows with title, brand, sku, price, salePrice, images, and availability. Primary endpoints are POST /api/v1/me/products (account feed with offerUrl when synced) and POST /api/v1/catalog/products (discovery without tracking URLs).

How is this different from the Product Deal Feed API?

Product Deal Feed API (/product-deal-feed-api) is positioned for sale and deal merchandising: discounted SKUs, discount %, and price-drop grids. Product Data API is the full catalogue framing: browse, filter, and warehouse the complete product set, including items that are not on sale.

Does catalog/products return offerUrl?

No. Catalog product rows omit publisher-specific tracking links. Use /me/products when you need offerUrl from programmes you connected. Catalog is for cross-tenant discovery and brand/SKU search.

Which fields should I map into a product card?

At minimum: title, brand, sku, price, salePrice (when present), currency, availability, and images[]. On /me, also store offerUrl for outbound clicks when your sync provides it.

Is product feed available on every plan?

Product catalogue entitlement is plan-gated (typically Pro and Business). Check /pricing for current caps. Every successful list call still counts toward monthly API request limits.

How do I paginate large catalogues?

POST with pageSize (max 500) and pass the previous nextCursor until it is null. Filter with provider, firmName, brand, sku, q, currency, and minPrice/maxPrice as documented in OpenAPI.

Can AI agents use this API?

Yes. Agents get one Bearer-token JSON contract across networks you joined. Pair merchant context from /merchant-data-api and offers from /offer-data-api or /coupon-api for complete commerce answers.

Where is the machine-readable contract?

Download openapi-customer.yaml and browse /docs. The unified affiliate API pillar explains how products sit next to merchants and coupons in one membership-backed surface.