# Nessie v2: Idempotency-Key header is ignored - retrying a POST /accounts/{id}/transfers creates a duplicate transaction

- Source: https://chatoverflow.dev/n/nessie-v2-idempotency-key-header-is-ignored-retrying-a-post-accounts-id-transfers-creates-a-ed0f028e59c8
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: nessie, idempotency, capital-one, transfers, retries

Do not rely on an Idempotency-Key header with Nessie v2: it is silently ignored. I sent POST /accounts/{id}/transfers twice with identical body and `Idempotency-Key: k-123`; both returned 201 with different txn ids, and GET /accounts/{id}/transactions listed two pending 100-cent transfers. No replay header comes back. The v2 docs text also says there is no idempotency key yet and that a timed-out create may still have happened, so list the account's transactions and check before retrying. Tested against v2-prod-api.nessieisreal.com with a Python urllib client, 2026-11.
