Getting started

Overview

Account questions need two things the bot cannot get from a knowledge base: proof that the person in the chat is the account holder, and read access to that person’s records. Every integration route on Silux Chat provides both in the same way, so the bot behaves identically whichever route you choose:

1. 1
   The customer asks something personal. The bot asks for their full name plus one more detail (postcode, email or mobile).
2. 2
   Your system (or your vendor’s system, through a connector) finds the account and sends a one-time code to the contact details already held on the account.
3. 3
   The customer types the code. A successful check returns a short-lived session.
4. 4
   Only then can the bot read the account, orders, invoices, bookings, subscriptions or tickets — and it answers from that data alone.

The three routes

1. Ready-made connectors (no code)

148 connectors cover the software businesses already run: Shopify, WooCommerce, Xero, QuickBooks, Stripe, Cliniko, Clio, Zendesk, HubSpot, ShipStation and many more. Open Dashboard → Integrations → Connectors, pick your software, paste a read-only API key (or sign in with the vendor where that is offered) and press Connect & test. The platform makes a real, read-only call to your account straight away and shows which capabilities work. A connector that can look customers up can then be switched on to verify them with Use to verify customers. Browse them all on the connectors page.

2. Account Connect (your own system)

If your customer records live in your own database or platform, add five small POST endpoints to it:verify-identity, verify-otp, account-summary, orders and invoices. Enter the base address and your API key once in Dashboard → Integrations → Account Connect and press Connect & test. Auto Trainer creates all five connections and runs the whole chain with a fictional test customer (Test Customer, postcode TE5 7ST, code 123456), so no real customer is ever texted. Reference code in Python, PHP and Node.js is in Build your own Account Connect endpoints.

3. No-code workflows and generic REST

Two connectors bridge anything else. Your own REST API calls a JSON API you already have (a customer lookup and an orders path, with a bearer token). Make / n8n / Zapier webhook posts each lookup to a workflow you build visually, which replies with JSON. See Webhooks, Make, n8n, Zapier & REST.

Choosing a route

What the bot can answer

Every route returns the same standard shapes, so the bot treats a Shopify order and an order from your own database identically.

Guides for each area: account lookups, billing & invoices, orders & delivery, bookings, subscriptions and support tickets.

The verification gate

The gate is enforced by the platform, not by the language model. Until the current conversation holds a valid session from verify-otp, the account tools simply do not run, whatever the customer types. This protects you from the most common attack on chatbots — persuading the bot to “just look up” someone else’s account.

Customer ──► "Where's my order?"
Bot      ──► asks for full name + postcode, email or mobile
Bot      ──► POST {base}/verify-identity    → {"success": true, "otp_token": "…"}
               (code sent to the contact details ALREADY on the account)
Customer ──► types the 6-digit code
Bot      ──► POST {base}/verify-otp         → {"success": true, "session_token": "…"}
Bot      ──► POST {base}/orders             → {"success": true, "orders": [ … ]}
Bot      ──► answers from that data only

• Codes are valid for 10 minutes and sessions for 30 minutes (Account Connect recommendation; enforced by the platform for connectors).
• After 5 wrong codes the code is destroyed and the customer must request a new one.
• A failed match never says which detail was wrong.
• If your system cannot be reached, the bot says it can’t check accounts right now — it never tells a real customer “no account found”.

10-minute quickstart

You can try the complete flow before writing any code. We run a live demo of the Account Connect endpoints with fictional customers at https://www.siluxchat.com/api/account-connect-demo/v1, API key demo-account-connect-key. Its code is always 123456 and no message is ever sent.

1. 1
   Call the demo from your terminal. Start with step 1 below; the full chain in four languages is in Testing with the live demo.
2. 2
   Point your dashboard at it. In Dashboard → Integrations → Account Connect enter the demo base address and key, then press Connect & test. Each of the five steps shows a tick.
3. 3
   Or try the demo connector. In Dashboard → Integrations → Connectors choose Silux Demo Store (try it), enter the key demo-account-connect-key and connect.
4. 4
   Chat as a customer. Open your bot and ask “where is my order?” as Test Customer / TE5 7ST, or as Jane Demo with jane.demo@example.com. Enter 123456 when asked.
5. 5
   Swap in your own system when you are ready — the bot needs no changes.

curl -s -X POST "https://www.siluxchat.com/api/account-connect-demo/v1/verify-identity" \
  -H "X-API-Key: demo-account-connect-key" \
  -H "Content-Type: application/json" \
  -d '{"full_name":"Test Customer","postcode":"TE5 7ST"}'

{
  "success": true,
  "otp_token": "eyJrIjoib3RwIiwiYyI6IkMxMDAxIiwiZXhwIjoxNzkwNDE2NTg2LjI4NDIyNDN9.443c18a766f3c03f371e3da90a269fdf",
  "message": "Code sent to mobile ending 000"
}

Public catalogue endpoints

Two endpoints need no authentication. Use them to build your own integration picker or to monitor our test results.

curl -s "https://www.siluxchat.com/api/connectors/catalogue"

{
  "count": 148,
  "categories": {"E-commerce": 13, "Payments": 11, "Accounting": 9, "CRM": 13, "Helpdesk": 12, "…": 0},
  "connectors": [
    {
      "key": "magento",
      "name": "Adobe Commerce / Magento 2",
      "category": "E-commerce",
      "capabilities": ["find_customer", "orders"],
      "auth": "bearer",
      "config": [{"name": "site", "label": "Store address", "example": "shop.example.com"}],
      "secrets": ["access_token"],
      "secret_labels": [{"name": "access_token", "label": "Integration access token"}],
      "docs": "https://developer.adobe.com/commerce/webapi/rest/",
      "setup": "Admin → System → Extensions → Integrations → Add New Integration (Customers, Sales read) → Activate → copy the Access Token.",
      "test_level": "documented",
      "note": null
    }
  ]
}

curl -s "https://www.siluxchat.com/api/connectors/smoke"

{
  "ran": "2026-09-26T09:46:35.862778+00:00",
  "passed": 148,
  "total": 148,
  "results": {
    "shopify": {"ok": true, "capabilities": {"find_customer": true, "orders": true}},
    "silux_demo_store": {"ok": true, "capabilities": {"find_customer": true, "orders": true, "invoices": true}}
  }
}

Next steps

• Authentication — the keys involved and how to rotate them.
• Customer identity verification & OTP — the exact matching rules and limits.
• Build your own Account Connect endpoints — the full specification and reference code.
• Security & data protection — for your DPO or security review.
• Troubleshooting & error reference — when a step shows a cross.

Get help

Not sure which route fits your systems? Email support@siluxcall.co.uk with the software you use and the questions you want the bot to answer, and our integration team will recommend the quickest safe route.