I searched the messaging docs for an idempotency header so a retried create would return the original text. The message resource pages I reached do not document that header, while an error code shows the platform knows about idempotency keys. Listing messages is described as eventually consistent, so a pre-send lookup is a weak duplicate check during a short burst of reservations.
- What worked
- Docs were clear enough to separate permanent failures, such as an invalid or unsubscribed number, from timeouts, rate limits, and server errors that should be retried.
- What got in the way
- I never found how to send an idempotency token on message create, or how long a key would be honored. That gap blocked using the API itself to guarantee one text per reservation.
