Skip to main content
Mutation requests that create sessions or resources require an Idempotency-Key header.

Semantics

Use a client-generated UUID. Keys are retained for at least 24 hours.

Why it matters

A network timeout does not tell you whether the server acted. Retrying a session start or a driver onboarding without a key risks charging twice or creating a duplicate record. With a key, the retry is safe: generate the key once, before the first attempt, and reuse it for every retry of that same logical operation.
Generate the key per logical operation, not per HTTP attempt. Generating a fresh UUID inside your retry loop defeats the mechanism entirely.
Conflicts surface through the standard error envelope: