Back
Todo
π‘οΈ Pro tip for building reliable Events APIs:
Network delays, retries & hiccups make duplicate events inevitable. (Double charges, repeated notifications, messed-up state - all bad.)
Fix it with idempotency_key:
β
Clients send a unique key (UUID works great) with every event
β
Your API stores processed keys in the DB (unique constraint).
β
Seen before? Ignore & return success.
β
New? Process & record it.
I just added full support for it in
#telesink.