Architecture

Neuroon is composed of three components distributed across two sides of the network: the widget (buyer's browser), the server API (your backend), and the Neuroon platform (our backend).

Hover or click a flow to see details.

The API you integrate

API	Prefix	Who calls it	Credential
Integrations	/api/integrations/v1/*	Your server	Authorization: Bearer <api-key>

Your server speaks HTTPS against api.neuroon.ai. Widget calls to the backend (searches, tracking) are handled internally by the widget bundle using the X-Widget-Token you inject via data-token — you don't have to code them.

End-to-end flow summary

1. You update the catalog: your server calls the Integrations API with POST /api/integrations/v1/products/sync (batches of up to 500). The product is searchable in 2 to 5 seconds.
2. The buyer searches: the widget renders results. You do nothing — the widget already handles the call to Neuroon.
3. The buyer buys: your server calls the Integrations API with POST /api/integrations/v1/conversions to close the loop.

Eventual consistency

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

Further reading

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