Idempotency key

A network timeout after a write actually succeeded is indistinguishable, from the client's side, from one that never reached the server — so retrying blindly risks creating the same document, connector or order twice. Sending the same Idempotency-Key on the retry tells the API “this is the same attempt”: it returns the original result instead of repeating the write.

Reusing a key with a different request body is rejected rather than silently accepted, so an idempotency key protects against duplicate side effects without masking a genuine bug in the retrying client.