APIs & Integration
Idempotency
The property that repeating the same request does not create unintended duplicate effects.
Example
Repeating the same payment request with one idempotency key creates only one charge.
Why it matters
It makes recovery safer when a request's outcome is uncertain.
You'll hear it
“The repeated request should not create a second order.”
Can you control it?
Set by the team
The people building or running the AI choose this setup. An everyday user generally needs their help to change how this part works.
Common questions
- Does idempotency mean the reply text is always identical?
- No. The important property concerns repeated effects, not necessarily identical wording or timing.
- Can it apply to only some actions?
- Yes. A service may support it for particular operations rather than everything.
- Does it automatically recognize every near-duplicate request?
- No. The system needs a clear way to decide which attempts represent the same intended action.