Idempotency

Send endpoints accept an optional Idempotency-Key header so you can retry safely after a network error:

curl -X POST https://api.blooio.com/v2/api/chats/%2B15551234567/messages \
 -H "Authorization: Bearer bl_live_..." \
 -H "Idempotency-Key: 1f3c9b6e-..." \
 -H "Content-Type: application/json" \
 -d '{ "text": "Hi" }'

Replaying the same key returns the original message_id and status (HTTP 200) instead of sending again, so a retried request never creates a duplicate message.

Use a unique key (such as a UUID) per logical send.

Send endpoints accept an optional Idempotency-Key header so you can retry safely after a network error:

curl -X POST https://api.blooio.com/v4/messages \
 -H "Authorization: Bearer bl_live_..." \
 -H "Idempotency-Key: 1f3c9b6e-..." \
 -H "Content-Type: application/json" \
 -d '{ "to": "+15551234567", "text": "Hi" }'

• Replaying the same key with an identical body returns the original result instead of sending again.
• Replaying the same key with a different body returns 409 Conflict.

Use a unique key (such as a UUID) per logical send.