How should idempotency and retries be designed for production in Web API?

Use idempotency keys for suitable commands, store request outcomes, define key lifetime, and make downstream effects consistent. The implementation should be justified by measurable requirements, kept as simple as the problem allows, and validated with realistic tests, telemetry, failure handling, and documented tradeoffs.