Idempotent requests¶
Stripe, I. (2026). Idempotent requests.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Request-Response
- Because a network failure can hide whether a charge request reached Stripe's servers, Stripe supports idempotency keys: the client generates a unique key (typically a UUID) and sends it in the
Idempotency-Keyheader with aPOST.This sourceStripe's own API contract for idempotency - a client-generated unique key, V4 UUIDs suggested, sent in the Idempotency-Key header, accepted on all POST requests. Stripe's own documentation of the retention window, which states that keys may be pruned once they are at least 24 hours old - a floor on retention rather than an exact expiry.
- Because a network failure can hide whether a charge request reached Stripe's servers, Stripe supports idempotency keys: the client generates a unique key (typically a UUID) and sends it in the
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:d4a7bfe3ad18 · see in the full table