Architecture

Neuroon sits between two ends of your integration: the shopper's browser (where the prebuilt widget runs) and your server (where your catalog lives). Only your server talks to Neuroon's API — the shopper never sees your Shop API Key.

Block view

Hover or click a flow to see details.

The API you integrate

API	Prefix	Who calls it	Credential
Plugin	/api/plugin/shops/*	Your server	Permanent X-Shop-API-Key + origin validation

Your server speaks HTTPS to api.neuroon.ai. Backend calls made by the widget (search, tracking) are handled by the widget bundle itself using the X-Widget-Token you inject into data-token — you don't have to code them.

End-to-end flow

1. You update the catalog: your server calls the Plugin API with products/sync (batches up to 500). The product is searchable in 2 to 5 seconds.
2. Shopper searches: the widget renders results. You do nothing — the widget already handles the call to Neuroon.
3. Shopper checks out: your server calls the Plugin API with track/conversion to close the loop.

Eventual consistency

After 200 OK from products/sync there is a short window before the product becomes searchable. If your E2E test fails searching for a freshly inserted product, wait a few seconds and retry with backoff.

No URL versioning

There is no /v1/, /v2/. Backward compatibility is kept by contract; breaking changes are announced upfront in the Changelog.

Next reads

• Quickstart — from zero to your first search in 5 minutes.
• Environments — Production vs Development.
• Authentication · Overview — which credential to use and when.