Zeni Chatbot - API Reference - Knowledge XML

Connect OpenCart, WordPress, WooCommerce, WHMCS, or a custom database to your chatbot by publishing an XML feed. The chatbot reads that feed from the Knowledge Bases tab, indexes it into a semantic search collection, and uses the content to answer visitors.

How to Connect a Platform

In the admin panel, open Knowledge Bases and download the example script for your platform (WordPress, OpenCart, WHMCS Orders, or General).
Copy the script to your store or site server (usually the platform root). Keep it reachable over HTTPS.
Open the script URL in a browser and confirm it returns valid XML (root <items> with one or more <item> entries).
Back in Knowledge Bases, add a new knowledge base, paste that HTTPS URL as the XML source, and assign a collection (for example products, support, or orders).
Save, then Index. Enable incremental updates when your feed supports the modified query parameter so only changed items are re-indexed.

Website embed and the visitor widget are separate from this API. This page covers only the XML feed used to sync catalog, content, or order data into your knowledge collections.

Required Structure

Wrap all records inside <items> and use one <item> per entry:

<items>
    <item>
        <id>123</id>
        <title>Example title</title>
        <description>Main body used for answers. HTML is accepted.</description>
        <category>Optional category</category>
        <price>Optional numeric price</price>
        <modified>2025-12-31 23:59:59</modified>
        <keywords>comma,separated,keywords</keywords>
        <url>https://www.example.com/item/123</url>
    </item>
</items>

<items>

<item>

<title>Example title</title>

<description>Main body used for answers. HTML is accepted.</description>

<category>Optional category</category>

<price>Optional numeric price</price>

<keywords>comma,separated,keywords</keywords>

<url>https://www.example.com/item/123</url>

</item>

</items>

Alternate entry tags are also accepted: <product>, <entry>, or <record> instead of <item>.

Field Specifications

id: Unique, stable identifier (string or number). Used to track updates and prevent duplicates.
title: Concise title for the indexed item.
description: Main content body. HTML is accepted (platform exporters often send HTML). Headings and useful text are kept; images inside the description can be extracted for answers. Put the exact product or page URL you want shared in <url>, and keep important facts in the text.
category: Optional grouping (for example electronics, support, billing).
price: Optional numeric value for product or order totals.
modified: Timestamp in YYYY-MM-DD HH:MM:SS. Enables incremental sync with ?modified=YYYYMMDDHHMMSS.
keywords: Comma-separated phrases that help matching and routing toward the right collection.
url: Public HTTPS URL for this item. The chatbot can share this link only when it appears in retrieved knowledge for the current question — use the real product/page URL, not a guessed path.

Implementation Guidelines

Protocol: Serve over HTTPS with Content-Type: application/xml (or text/xml) and UTF-8 encoding.
Collection assignment: Each XML feed is linked to a collection in the Knowledge Bases tab. Use separate collections for products, policies, and orders when possible.
Incremental sync: Append ?modified=YYYYMMDDHHMMSS so only items changed after that timestamp are returned. The example scripts support this filter.
Encoding: Escape XML special characters (&, <, >). CDATA is fine for HTML descriptions.
Item count: Optional count on <items> helps progress tracking: <items count="123">.
Output modes: Example scripts can stream XML in the HTTP response (recommended for the knowledge base URL) or write a local file.

Platform Exporters

Download these from the Knowledge Bases tab. Host each script on the matching platform, then paste its public URL into a knowledge base entry.

General: Template for any MySQL database. Map your SQL columns to id, title, description, and the other fields.
WordPress (+ WooCommerce): Exports posts, pages, and WooCommerce products when WooCommerce is installed. Supports ?modified=YYYYMMDDHHMMSS and ?lang=xx (WPML / Polylang). Expands shortcodes into final HTML where possible.
WordPress Orders (WooCommerce): Exports order records for order-related collections.
OpenCart: Exports products using OpenCart config.php database settings when available.
OpenCart Orders: Exports orders for order-related collections.
WHMCS Orders: Exports WHMCS order data for billing/order collections.

For products or catalog content, assign an eshop/products-style collection. For order exports, assign an orders collection and set the collection intention accordingly in Routing.

Sample Minimal Feed

<items count="2">
    <item>
        <id>1</id>
        <title>Shipping policy</title>
        <description>We ship worldwide within 5 business days.</description>
        <modified>2025-11-01 10:00:00</modified>
        <keywords>shipping,delivery,policy</keywords>
        <url>https://www.example.com/policies/shipping</url>
    </item>
    <item>
        <id>2</id>
        <title>Return window</title>
        <description>Returns accepted within 30 days with receipt.</description>
        <modified>2025-11-01 10:05:00</modified>
        <url>https://www.example.com/policies/returns</url>
    </item>
</items>

<item>

<title>Shipping policy</title>

<description>We ship worldwide within 5 business days.</description>

<keywords>shipping,delivery,policy</keywords>

<url>https://www.example.com/policies/shipping</url>

</item>

<item>

<title>Return window</title>

<description>Returns accepted within 30 days with receipt.</description>

<url>https://www.example.com/policies/returns</url>

</item>

</items>

Checklist After Connecting

Open the script URL and confirm the XML loads without login prompts or HTML error pages.
Confirm each item has a stable id, a clear title, useful description text, and a correct public url when you want the bot to share links.
Index the knowledge base, then ask a few real product or policy questions in the widget or team chat.
If answers miss updates, re-index or enable automatic indexing for that source.