Set Up Real-Time Data Feed Max on Drupal

Expose Drupal content or Commerce products as a 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.

Option 1 — JSON:API (built in, recommended)

Drupal 8.7+ ships with JSON:API as a core module. Once enabled, every content type is instantly available as JSON at a predictable URL — no custom coding.

Enable the JSON:API core module Drupal admin → Extend → search for JSON:API → tick and install. No contrib download needed.

Check anonymous read permission Drupal admin → People → Permissions → make sure Anonymous has access to the content types you want to expose. JSON:API respects Drupal's standard permissions.

Build your feed URL The format is /jsonapi/node/{content_type}. Append field filters to keep the response small.

https://your-site.com/jsonapi/node/article?page[limit]=50&fields[node--article]=title,body,path

Replace article with your content type machine name (e.g. product, faq, page, news).

Option 2 — Views REST Export (full control)

For more control over which fields are returned and how they're shaped (e.g. combining multiple content types, custom filters), build a custom REST view.

Enable RESTful Web Services Drupal admin → Extend → enable RESTful Web Services, Serialization, and REST UI (contrib) for easier config.

Create a new REST export View Structure → Views → Add view → tick Provide a REST export → pick a path like /ai-feed.json. Add the fields you need and map them to our format.

Paste the view URL into Real-Time Data Feed Max For example, your-site.com/ai-feed.json.

Option 3 — Drupal Commerce Products

If you're on Drupal Commerce, products are a separate entity (commerce_product). Expose them via JSON:API:

https://your-site.com/jsonapi/commerce_product/default?page[limit]=50

Drupal Commerce products have price, variations, and stock levels as related entities — you may want to use JSON:API's include parameter (?include=variations,variations.price) or build a Views REST export for a flatter, cleaner output.

Tip: JSON:API paginates at 50 items per page by default. If you have more than 50 items, use a Views REST export (Option 2) with no pagination — it returns everything in one response.

Troubleshooting

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.

Documentation