Idempotency

curl https://api.sendbaze.com/v1/emails \
  -H "Authorization: Bearer $SENDBAZE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-1042-shipped" \
  -d '{ "from": "orders@yourshop.co.za", "to": "thandi@example.com", "subject": "Shipped", "text": "Tracking: CG123456789ZA" }'

await sendbaze.emails.send(email, { idempotencyKey: "order-1042-shipped" });

requests.post(url, headers={**headers, "Idempotency-Key": "order-1042-shipped"}, json=email)

​

How it behaves

• Same key, same body within 24 hours: the original response is returned with the header Idempotent-Replayed: true. Nothing is sent again.
• Same key, different body or channel: 409 idempotency_conflict. A key identifies one logical send; do not reuse it for a new message.
• Request failed before the message was queued (validation, suppression, allowance): the key is released, so a corrected retry goes through.
• After 24 hours the key is released.
• Keys are up to 255 characters and scoped to your organisation. Something you already have is the best key: an order id plus the event, a job id, a UUID you store with the record.

​

Where it matters

• Job queues that retry on failure (Sidekiq, Celery, BullMQ, SQS consumers).
• Serverless functions that may run more than once for one trigger.
• Any client that retries on timeout, which should be every client.