What is a common mistake when working with API idempotency?

A common mistake with API idempotency is implementing the happy path only and leaving production concerns such as validation, security, retries, timeouts, ownership, monitoring, failure recovery, and backward compatibility until later. This usually creates fragile behavior that is difficult to diagnose once the system is under real load.