OTP & Transactional
Idempotency keys for OTP sends
Stop double-sending when a retry happens on your side. Pass an idempotency key and we deduplicate.
2 min readUpdated 14 Mar 2026
If your application retries a send request because of a network blip, you can end up sending two OTPs to the same user. Idempotency keys prevent this completely.
How to use them
- 01Generate a unique key (we recommend a UUIDv4) for each OTP request.
- 02Pass it in the Idempotency-Key header on POST /v2/otp/send.
- 03If the same key arrives within 24 hours, we return the original response without sending a second OTP.
- 04Keep the key until you receive a terminal status (delivered, failed, or expired).
Related articles in OTP & Transactional
Browse other help categories
Getting started
Create your account, add credits, and send your first message in under fifteen minutes.
SMS campaigns
Templates, DLT routing, sender IDs, delivery reports, scheduling, and retries.
WhatsApp Business API
Onboarding, template approval, chatbot flows, team inbox, quality rating, and analytics.
AI WhatsApp Agents
Train your agent, sync your catalogue, set handoff rules, and go multilingual.
Did this article help?
If something isn't clear or the steps don't match what you're seeing, tell us and we'll fix the doc the same day.