Custom store / API connector
If your store is not on Shopify or PrestaShop — it runs on another platform or a custom backend — connect via the API connector. You send data through the public API and the panel treats it like data from ready-made integrations.
Integrations page — platform choice including Custom / API path. (illustrative screenshot — in progress)
When to choose this path
- Store on a platform outside the catalog (e.g. custom e-commerce system).
- You have your own backend and want full control over what and when you send.
- You need a tailored integration and a ready connector is not enough.
What you send via API
The same API covers the full cycle:
- Product catalog — items needed for upsell recommendations.
- Customers — contact and personalization data.
- Orders — enter the queue and qualify for calls.
- Repurchase intents — signals that a customer is ready to buy again, usable in conversation.
It is one API for both regular orders and repurchase intents — you do not need a separate integration for each case.
Quick start
Get an API key
You receive the key in the panel. Treat it like a password — do not put it in
public code or links. In the panel the key is always masked, e.g.
cba_test_••••••••, so you only see a fragment.
Send first data
Send products, customers, and orders per API documentation. Start with a few test records to confirm fields map correctly.
Verification and diagnostics
- Products or orders missing? Confirm you send to the correct endpoint and the API key is active.
- Order does not qualify for a call? Usually rules (hours, consents, payment classification), not the connection — see Connector readiness blockers.
- Repeated submissions — design integration so retrying the same request does not create duplicates (idempotency in API docs).
Full technical documentation
Details for your implementation team — authentication, idempotency, webhooks, and error codes — are in API and integrations: