From c67bb256eb0f6dde23e99d7a3638729e851d74d8 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 4 Aug 2026 21:08:54 +0000 Subject: [PATCH] docs(sms): note E.164 recipient requirement for SMS sends The hosted API now rejects a non-E.164 SMS `to` with 400 invalid_recipient instead of accepting it and failing at dispatch. Note the requirement next to the SMS send_raw example so callers format numbers correctly. Co-Authored-By: Claude Opus 4.8 (1M context) Claude-Session: https://claude.ai/code/session_01MyKX5gt1HHZoV2YW4729qs --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index 188cb63..0f983ff 100644 --- a/README.md +++ b/README.md @@ -158,6 +158,9 @@ sk.send_raw(subscription_json, WebPushContent(title="Back in stock", body="Tap t click_url="https://example.com/item")) ``` +SMS recipients must be an [E.164](https://en.wikipedia.org/wiki/E.164) phone number +(e.g. `+15555550123`); a non-E.164 `to` is rejected with `400 invalid_recipient`. + ### Batch Sends many messages concurrently (a thread pool for sync, `asyncio` for async). A failed