Guide

Idempotency

Retry-safe writes without duplicate side effects.

When to use it

Send Idempotency-Key on POST, PATCH, and DELETE. Replays with the same key and body return the original result. A different body with the same key returns idempotency_conflict.

curl https://api.statxe.com/api/v1/contacts \
  -X POST \
  -H "Authorization: Bearer stx_live_xxx" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: contact_sync_123" \
  -d '{"email":"ada@example.com","first_name":"Ada"}'

Key design

Use a stable business identifier (CRM contact id + operation) or a UUID per logical write. Do not reuse a key across unrelated operations.