Idempotency key on transactional messages

Transactional (email) messages are not idempotent by nature. It would be good if the CustomerIO API and SDKs would support e.g. an idempotency key to ensure that message are not sent twice even in case of network timeouts and subsequent retries from the client.

Start by reviewing the CustomerIO API and Python SDK paths for transactional email messages, then trace how requests are retried after network timeouts. Define how an idempotency key is accepted and propagated, and confirm that repeated retries do not send the same message twice.

Vom Indexierungsmodell aus dem Issue-Text verfasst.