Executed local demonstration · Python + SQLite
A repeated webhook.
One stored receipt.
An integration may send the same event again. This small HTTP component returns the recorded result for an identical retry and rejects a reused key with different data.
Fictional data, real local HTTP requests. The page displays recorded results; it does not run requests against your systems.
—concurrent copies of one event
SQLitekey, payload hash and stored receipt
—recorded outcome loading
Loading the recorded results…
Inspect a test
Select a case to see the response observed during the recorded run.
Recorded evidence
Results loading
No result loaded.
See every result
Every case above comes from a recorded run on a real server. The full results file is here; the package itself is delivered with your order.
What the evidence covers
- The only stored effect is a fictional SQLite receipt. No email, payment, CRM record or external API operation is performed.
- Retries are compared after normalizing the supported name and status fields. Reusing the key with a different supported payload returns a conflict.
- Concurrent requests use one SQLite database file. A clean server restart can be tested against that same file; this is not a crash-recovery or distributed exactly-once guarantee.
- The API key is a public demo value. The server binds to localhost and is not a production deployment. TLS, authentication, retention and external side-effect recovery require a separate design.