Idempotency keys for microservice writes?

Hey everyone, I've been pondering how to make our microservice writes more dependable. Specifically, when a client sends a POST request to create something, how are you all dealing with the chance that the client might retry that request because of network glitches? Just counting on the database's built-in idempotency, like unique constraints, seems a little shaky to me. Are you folks using explicit idempotency keys in the headers? And if you are, how do you handle managing them on the server side? I'm really interested in hearing your experiences and what common approaches you've seen.