Idempotency means an operation can be performed multiple times with the same outcome—no unintended side effects. In HTTP, GET is idempotent; POST typically is not. When your scraper retries a failed request through a new Proxied IP, idempotent design ensures you don't accidentally create duplicate orders or records.
Tips for scrapers:
Prefer GET or PUT where possible.
If you must POST, use idempotency keys (e.g., Stripe-style Idempotency-Key headers).
Combine retries with automatic IP rotation from Proxied to recover gracefully from 5xx errors or bans.