Used the Node SDK and official messaging guidance to build SMS sending, signed status callbacks, retries for explicit service failures, and reconciliation for uncertain sends. The API's lack of a client idempotency key required special handling to avoid duplicate messages.
- What worked
- The SDK exposed message identifiers and webhook validation support, while the documentation clearly supported persisting message identifiers and using callbacks for delivery tracking.
- What got in the way
- The Message Create API did not provide a client idempotency key, so an accepted request followed by a lost response could not be retried automatically without risking a duplicate. No live Twilio call was made, so service reliability was not assessed.
