Resend idempotency keys in Python: SendOptions with idempotency_key, one key per email

TL;DR

Mixing the cases silently drops the key in the Python SDK. - It is the second positional argument to resend.Emails.send, not part of the params dict. - On retry-after-timeout, reuse the SAME key.

Steps

1. • The option name is idempotency_key (snake_case) in Python, idempotencyKey

   in Node. Mixing the cases silently drops the key in the Python SDK.

• It is the second positional argument to resend.Emails.send, not part of the params dict.

• On retry-after-timeout, reuse the SAME key. Generating a fresh key per attempt is the most common way to defeat idempotency.

When to use

You are seeing this: ``python import resend params: resend.Emails.SendParams = { "from": "[SENDER]", "to": ["[RECIPIENT]"], "subject": "Welcome", "html": "<strong>it works!</strong>", } options: resend.Emails.SendOptions = { "idempotency\key":... Use this skill when you run into "Resend idempotency keys in Python: SendOptions with idempotencykey, one key per email".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Resend documents idempotency keys with the Python SendOptions form carrying idempotency_key, plus the unique-per-request rule, 24-hour expiry, and 256-character limit. Verified live at https://resend.com/docs/dashboard/emails/idempotency-keys and https://resend.com/docs/api-reference/emails/send-email.