- Shipped
- September 7, 2026 at 12:06 AM UTC
- Author
- Kamo
- Commit
- 0b28dce
An administrator adding a text provider has to paste Kamo's inbound URL into the carrier's own console, and nothing told them what it was. Missing that step has no symptom on the side anybody tests first: messages send perfectly and every reply is dropped. GET **************** answers it. Served rather than hardcoded in the browser for the reason RingCentral's redirect URI is served: the value comes from a deployment property, and a copy in the frontend keeps confidently displaying the old host after the real one moves. The URL now has ONE definition. TelnyxProvisioner WRITES it into the customer's messaging profile and the settings screen SHOWS it to somebody pasting it by hand; when those were two strings nothing would have failed if they drifted — an administrator would simply have been instructed to configure a URL nothing listens on. InboundWebhookUrls is that definition, and its test asserts that every slug it builds resolves back through InboundSmsNormalizer, so the two sides agree by construction rather than by a table somebody must remember to update. The endpoint also reports whether a carrier's inbound is genuinely wired — a signature check AND a parser. Handing somebody a URL for a carrier whose payloads nothing can read would be an instruction to configure something that then refuses every message, which is worse than saying plainly that it is not supported yet.