Fictional data · Local service
01 / Callback reliability
Send the same
delivery twice.
A retry should receive an acknowledgment without creating another event. Compare that with a changed body, an invalid signature and an older update.
Stored eventsLoading
Demo shipmentLoading
Latest responseNot run
Try a delivery
One event ID.
Different outcomes.
Start with the first event. Each button calls the local Python service and refreshes its SQLite records.
No external API or real shipment is contacted. This is a narrow receipt-handling demonstration, not a production integration.
Response journal
0 session attemptsThe first response will appear here.
Persisted events
Most recent first| Event ID | Shipment | Status | Event time, UTC |
|---|
On a narrow screen, scroll the table to see the event time.
Loading stored state.