Start
Test mode
Every shop gets test mode for free. A test key (uc_test_…) works on the same routes as a live key, against a separate set of test data. Build your connection against it, and keep running it in your CI. Nothing you do with a test key reaches a shopper.
What a test key can and cannot touch
A key works in its own mode and nowhere else. A test key reads and writes test data only, and a live key never sees test data. The key decides the mode, and nothing in a request can change it. GET /v1/shop tells you which mode a key works in.
| Test key | Live key | |
|---|---|---|
| Prefix | uc_test_ | uc_live_ |
| Data | Test data only | Live data only |
| WhatsApp messages | Kept by Uncart, never sent | Sent to shoppers who agreed |
| Orders | Checked, never matched or billed | Matched and billed |
| Cost | Free | 15% of orders placed within 3 days of a tap on an Uncart link, €10 minimum (pricing) |
What happens to messages in test mode
A test key sets off no message. A test key's cart, order or refund is checked and answered as a live key's is, against your test catalogue, and nothing is kept or queued: no basket, no reminder, no message.
What happens to orders in test mode
A test key's order is checked and answered, and never matched or billed: its click id answers unknown. A test link (POST /v1/test-links with a test key) leads to your page with uc_click in its address, so you can check that your page keeps the click id and sends it with the order. Only a live key's round trip takes your shop live.
Going live
A shop sends its first real message only when two things are true. Its billing is connected, and a round trip has passed. In a round trip, a test link was tapped, and a test order carrying its click id was reported and matched. Sending then pauses by itself if order reports stop, or fall far below link taps against the shop's own history. The dashboard shows why under "Needs you".