Guides
Idempotency
Contract
Every mutating endpoint accepts an Idempotency-Key header — required on most POSTs. Send a unique key per logical mutation (uuid or stable id + suffix).
Replay
A second request with the same key returns the stored response — same status code, same body — without re-running the mutation. Keys are scoped to your organisation, project and environment.
Example
curl https://app.bondmako.com/api/v1/invoices \
-H "Authorization: Bearer bm_test_…" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{ … }'