Set Up Real-Time Data Feed Max on Magento / Adobe Commerce

Three ways to expose your Magento catalog as a public JSON feed

Pro-plan

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.

How Magento Differs

Magento's REST API requires an integration access token — there's no public product endpoint out of the box. Your three options are: a product feed extension (easiest), a proxy calling the REST API (most control), or a custom Magento module (most integrated).

Option 1 — Product Feed Extension (easiest)

Several Magento Marketplace extensions generate a public JSON feed at a fixed URL with no code required.

Mirasvit Advanced Product Feed
Simple Google Shopping Feed
Wyomind Data Feed Manager
Amasty Product Feed

Install and configure the extension Follow the vendor's install steps (usually via composer require + bin/magento setup:upgrade).

Create a new feed Pick JSON as the output format. Map your product fields to our format: name, price, description, image_url, button_link, in_stock.

Generate and publish the feed The extension will give you a public URL (usually under /pub/media/ or /feeds/).

Paste the URL into Real-Time Data Feed Max Most extensions let you schedule daily regeneration — set it so your feed stays current.

Option 2 — REST API via a Proxy

If you prefer not to install extensions, use Magento's built-in REST API through a small proxy.

Create a Magento Integration Magento admin → System → Extensions → Integrations → Add New Integration. Grant Catalog → Products (read-only) under API access.

Activate and copy the Access Token After activation, Magento shows a 32-character Access Token — copy it for your proxy.

Call the REST endpoint from a proxy The proxy calls GET /rest/V1/products?searchCriteria[pageSize]=250 with the token, reshapes the output, and returns public JSON.

GET https://your-site.com/rest/V1/products?searchCriteria[pageSize]=250
Authorization: Bearer YOUR_ACCESS_TOKEN

Option 3 — Custom Magento Module

For teams with Magento development expertise, build a lightweight custom module that registers a public REST endpoint. This avoids the extra infrastructure of a proxy but requires PHP development time.

The module would define a webapi.xml route with anonymous ACL, and a service contract that loads products and transforms them into our JSON format. The feed URL becomes part of your own Magento installation.

Which option? Start with Option 1 unless you already have a feed extension you dislike. Option 2 is best if you want total flexibility without vendor lock-in. Option 3 is for teams already deep in Magento dev work.

Fejlfinding

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.

Dokumentation