Idempotency

Creates, duplicates, divides, applies, bulk changes, and destructive operations require Idempotency-Key. Keys contain 16-128 printable ASCII characters and are namespaced by owner, API key, API major version, operation ID, and the supplied key.

Committed successful responses are cached for 24 hours. Failed/uncommitted attempts are not cached. The cache never stores a reusable plaintext API-key secret; one-time key creation/rotation responses use a redacted replay-safe representation and require callers to preserve the originally returned secret themselves. Replaying the same normalized request returns the committed outcome; reusing the key with a different payload returns idempotency_conflict.

After a timeout, retry the exact request with the same key. Do not invent a new key until the prior outcome is known.