Sume Format run idempotency key: order id plus version, not uuidgen

Derive the Sume Format run Idempotency-Key from your order id plus a version. A fresh uuidgen per request makes the header do nothing and double-bills retries.

5 min readSume
All posts

Derive the Idempotency-Key for a Sume Format run from the thing the run makes, such as your order id plus a version: order-8823-lc-v1. A new uuidgen on every request means the header has no effect, so a retried create starts a second run and a second bill. With a stable key, the same body returns a 200 replay of the first run, where a fresh create returns 202. Source: Create a Format run, read 2026-10-06.

What happens on each retry?

Sume compares the key and the body.

Idempotency outcomes, read 2026-10-06 from docs.sume.com.
RequestResult
Same key, same body200, replay of the original run
Same key, different body409 idempotency_conflict
Concurrent duplicate409 idempotency_key_in_use
New key202, a new run

How do I handle a real change?

Bump the version in the key. If the order changes, order-8823-lc-v2 is a different request on purpose, and it can reference the earlier run with previous_run_id. Keep the key to ASCII and stable across your own retries.

Sources

Related posts

More in Formats

All Formats posts

Written by Sume