Skip to content

docs(sms): note E.164 recipient requirement for SMS sends - #21

Open
tuyakhov wants to merge 1 commit into
mainfrom
claude/gallant-einstein-7pj3eq
Open

docs(sms): note E.164 recipient requirement for SMS sends#21
tuyakhov wants to merge 1 commit into
mainfrom
claude/gallant-einstein-7pj3eq

Conversation

@tuyakhov

@tuyakhov tuyakhov commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Summary

The hosted API now enforces that an SMS recipient (to) must be an E.164 phone number. A non-E.164 SMS to is rejected with 400 invalid_recipient instead of being accepted and failing later at dispatch.

Note the requirement next to the SMS send_raw example so callers format numbers correctly. This mirrors the same doc update landing in the TypeScript and PHP SDKs.

Related issues

Checklist

  • ruff check . passes
  • ruff format . applied
  • mypy src passes
  • pytest passes (new behavior is covered by tests)
  • PR title / commits follow Conventional Commits (drives versioning & changelog)
  • Docs / docstrings updated if the public API changed

Docs-only change (README); the linter/type/test items above are unaffected.

🤖 Generated with Claude Code


Generated by Claude Code

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) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MyKX5gt1HHZoV2YW4729qs
@codecov

codecov Bot commented Aug 4, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants