Set Up Real-Time Data Feed Max on Ecwid

Expose your Ecwid catalog using the Storefront REST API

Pro план

What Your Feed Should Look Like

Real-Time Data Feed Max accepts any public URL returning JSON or plain text. The AI reads whatever you give it — products, services, bookable slots, property listings, menus, opening hours, anything — and uses it to answer visitor questions. There is no required shape or field name.

The one exception is Dynamic Product Cards. If you want matching items to render as visual cards in the chat, use these specific field names: name, price, description, image_url, button_link, in_stock.

Example — products (triggers Dynamic Product Cards)

{
  "products": [
    {
      "name": "Wireless Headphones Pro",
      "price": "$149.99",
      "description": "Premium over-ear wireless headphones with ANC.",
      "image_url": "https://example.com/images/headphones.jpg",
      "button_link": "https://example.com/products/headphones",
      "in_stock": true
    }
  ]
}

Example — services (any shape works)

{
  "services": [
    {
      "service": "Deep tissue massage",
      "duration_minutes": 60,
      "price_from": "$95",
      "therapists_available": ["Anna", "Mark"],
      "booking_link": "https://example.com/book/deep-tissue"
    },
    {
      "service": "Haircut & style",
      "duration_minutes": 45,
      "price_from": "$55",
      "booking_link": "https://example.com/book/haircut"
    }
  ]
}

Example — plain text (works too)

Opening hours: Mon-Fri 9-6, Sat 10-4, closed Sunday.
Delivery: Free over $30, minimum order $15, within 5 miles.
Lunch specials (weekdays only):
- Margherita pizza $12
- Caesar salad $9
- Soup of the day $7

Rule of thumb: Use descriptive field names the AI can interpret (service, duration, price, location, etc.). If Dynamic Product Cards make sense for your business, follow the exact field names above. If they don't, use whatever shape fits your data — the AI still searches it and answers questions correctly.

Option 1 — Public Storefront Token (simplest)

Ecwid offers a read-only public token designed specifically to be used client-side. You can paste the resulting URL directly into Real-Time Data Feed Max — no proxy required.

Find your store ID Ecwid admin → My Profile (top right) → shown as a number, e.g. 12345678.

Generate a public API token Ecwid admin → Apps → My Apps (or Legacy: Settings → API) → create an access token with read_catalog scope. Look for the Public Token variant — it starts with public_ and is safe to include in URLs.

Build your feed URL Use the format below, substituting your store ID and public token.

Paste into Real-Time Data Feed Max Test the URL in a private browser window first — you should see JSON with an items array.

https://app.ecwid.com/api/v3/YOUR_STORE_ID/products?token=public_YOUR_PUBLIC_TOKEN&limit=100

Public vs. private token: Only use the Public Token (starts with public_) in URLs. The Secret Token grants write access and must stay server-side.

Option 2 — Proxy with Reshaped Fields (recommended for product cards)

Ecwid's native JSON uses its own field names (name, defaultDisplayedPriceFormatted, thumbnailUrl, url, inStock). To make Dynamic Product Cards render correctly, run the response through a small proxy that renames fields.

// Cloudflare Worker example
export default {
  async fetch() {
    const r = await fetch(
      'https://app.ecwid.com/api/v3/YOUR_STORE_ID/products?token=public_YOUR_TOKEN&limit=100'
    );
    const data = await r.json();
    const products = data.items.map(p => ({
      name:        p.name,
      price:       p.defaultDisplayedPriceFormatted,
      description: (p.description || '').replace(/<[^>]+>/g, '').slice(0, 200),
      image_url:   p.thumbnailUrl,
      button_link: p.url,
      in_stock:    p.inStock,
    }));
    return new Response(JSON.stringify({ products }), {
      headers: { 'Content-Type': 'application/json' },
    });
  }
};

Савет: Ecwid's products endpoint paginates at 100 items per request. For larger catalogs, have your proxy loop through pages using the offset parameter until you've fetched everything.

Решавање проблема

I see a password page instead of JSON

Your site is in maintenance, staging, or password-protected mode. Real-Time Data Feed Max needs a fully public URL.

Real-Time Data Feed Max says the feed failed

Open the URL in a private browser window. If you don't see JSON, the URL is wrong or the endpoint is down. If you see JSON but we still fail, the response may be missing a Content-Type: application/json header or exceeding the 10,000,000 character limit.

Product cards don't render

Dynamic Product Cards require specific field names (name, price, image_url, button_link, in_stock). If your platform uses different names, reshape the response in a small custom script before exposing it.

Data looks wrong or outdated

The feed auto-refreshes every 24 hours. For immediate updates, click Refresh Now in Real-Time Data Feed Max. For live fields (price, stock), the AI pulls fresh data on every message — so the 24h cycle only affects which items are known, not their current state.

Feed size exceeded

Real-Time Data Feed Max accepts up to 10,000,000 characters (~25,000 items). If you exceed that, trim fields (skip long HTML descriptions), split your catalog, or use the standard Real-Time Data Feed alongside for secondary data.

Still stuck? Start with the simplest option for your platform and verify the URL works in a browser before pasting it into Real-Time Data Feed Max. You can always upgrade to a more advanced option later — only the URL field changes on our side.

Документација