Idempotency
The property that repeating a request produces the same effect, which is what makes a retry safe to send after a timeout.
- Category
- API & Models
- Also known as
- Idempotency key, Idempotent request
- Related terms
- 5
- Directory entries
- 16
- Docs
- docs.typesafe.ai
- Added
- 2026-10-12
Definition
An idempotent request can be sent again without changing the outcome, so a client that times out can retry without risking a double effect. A question that only reads a state is naturally idempotent; a request that also triggers an action is not, and needs a key to be deduplicated.
It is the precondition for the retry policies the SDKs apply: retrying is only safe because a repeated decision returns the same answer. When the decision feeds a side effect, put the idempotency in the code that performs the effect, not in the model call.
Related terms
Definitions that connect to this one.
From the Jev directory
10 more matching entries in the full directory.
From the Jev community
Posts from builders shipping with Jev right now.