Receiving inbound SMS over HTTPS

Route inbound SMS for a cloudnumbering number to your HTTPS webhook.

Before you start

Your webhook must be publicly reachable over HTTPS with a valid certificate.

Configure inbound SMS in the portal

Sign in to the cloudnumbering portal.
Go to Number Management > Endpoints.
Select Create Endpoint.
Enter an Endpoint Name.
Set Endpoint Type to SMS.
In Hostname, choose https:// and enter your webhook hostname and path.
Select Create Endpoint.
Go to Number Management > Number Inventory and open the receiving number.
Choose the endpoint under SMS Endpoint and turn on Enabled.
Select Save.

Allow inbound SMS webhook source IPs

If your firewall filters incoming requests by source address, allow HTTPS requests from all three fixed cloudnumbering source IP addresses:

13.41.154.11
18.135.51.94
18.171.64.227

Callbacks can originate from any of these addresses, so allow all three.

Note: These addresses are also used for outbound SMS delivery receipt callbacks. See Receiving SMS delivery receipts.

Source-address filtering is not cryptographic authentication. Treat webhook fields as untrusted input and follow the safe-processing guidance in Receive inbound SMS with an HTTPS endpoint.

What happens next

cloudnumbering sends inbound messages to the assigned HTTPS endpoint. Making an endpoint the default can apply it to later routing decisions, but it does not change numbers that already have an explicit endpoint.

Troubleshooting

My webhook receives no requests

Check that the intended endpoint is assigned to the number, SMS routing is Enabled, the URI starts with https://, DNS resolves publicly, and the certificate is valid. If your firewall filters source addresses, confirm that it allows all three inbound SMS webhook addresses.

Delivery stopped after working previously

Check the certificate expiry and chain, then review your server logs for connection failures and non-2xx responses. Confirm that your firewall still allows all three inbound SMS webhook addresses.

My handler rejects the sender

The sender can be an E.164 number or an alphanumeric sender ID. Treat it as untrusted text and follow the validation guidance in the developer guide.