Open the first case
Use the button above. Case 02 opens the calculate alias with its request and selector already matched.
START HERE · LOCAL MOCK
Make your first
Touchpoint request.
Explore the API, send a complete basket and follow the integration sequence. The mock and Swagger UI are ready to use here.
Run the first item →Explore all endpointsSimulation, clearly scoped. Fixed responses and synthetic data. No live POS, payment, fiscal operation or real credential. The mock does not store basket state.
USE IT LOCALLY
Download the complete kit.
The same version as this portal, including Mockoon, Swagger UI, OpenAPI, every scenario and the PDF/Markdown guide. No repository access required.
Extract the ZIP and run docker compose -p czz-touchpoint-kit up -d from its folder. Open http://127.0.0.1:15116 to use it locally.
01 / FIRST REQUEST
Open. Execute. Inspect.
Press Execute
The public demo key is preloaded. The request contains SCO-01, a basket identity and the first item.
Check HTTP 200
Expect one accepted line a1, total: 2 and totalSaving: 1. Inspect the complete response below the request.
02 / FOLLOW THE SEQUENCE
Build the basket. Then finish.
Each link opens a matching request and selector in Swagger. Send the full basket at each step; preserve its identity and use the latest digest for finish.
- 02First itemStart a basket
- 03Second itemKeep accepted lines
- 04Third itemComplete the basket
- 14LoyaltyObtain the new digest
- 10FinishSubmit the digest from 14
- 10rRetrySame identity and digest
The supplied requests already carry coherent values. This demonstrates the wire sequence, not live state or idempotency. Manual POS actions are described separately in the guide.
03 / CHECK THE FAILURE PATHS
See what your client must handle.
Rejected item
HTTP 200 can still contain a rejected line. Inspect rejected.
Stale digest
Inspect the recalculated basket before asking for confirmation again.
Case 09 →Already paid
Observe the simulated conflict and handle the operation boundary.
Case 10c →For HTTP 403, open Authorize in Swagger and clear the demo key. For HTTP 400, select MOCK_ONLY_INVALID_SELECTOR for X-Mock-Case on an integration alias while keeping valid authorization. Restore the demo by reloading the page.
04 / SCENARIO CATALOG
Every input. Every expected output.
Use a scenario endpoint for a single case, or an integration preset to exercise calculate/finish.
| Case | Scenario | HTTP | Try it | JSON files |
|---|
Keep the reference close.
The guide covers authentication, sequences, all startup methods and the transition to a real installation.