The plain-English version
A caller-provided identifier that a supporting operation uses to associate repeated requests with one intended operation.
Why it matters
It separates retry identity from an accidentally new request after an uncertain network result.
Let’s make it click
A test client retries an interrupted create operation with the same key and compatible parameters according to the provider contract.
Vibe Bro’s heads-up
Changing the key on every retry defeats that purpose. Retention, supported operations, concurrent requests, and stored error behavior vary by service.
You might also hear
- request retry identity
- deduplication key
- idempotent request
Vibe Bro’s field notes
Read the provider contract; avoid putting personal data or credentials in keys.
The docs behind it
Research sources reviewed .
Editorial review · October 28, 2026
Supported: Stripe's current request contract confirms client-generated keys, compatible retry parameters, retained errors, and retention/version-dependent semantics; the entry correctly defers all such details to the chosen operation.