Andrews & Arnold and Custom HTTPS

Use these connections when SessionCloud should manage the app’s inbox and send outgoing text messages through an HTTPS gateway. For an app that contacts your server directly, use Customer-hosted service. For standalone app settings, use HTTPS SMS.

Configure the connection

1. Open Provisioning > Advanced > Messaging in your BYO PBX project and enable SMS.
2. Select Andrews & Arnold or Custom HTTPS under the messaging providers.
3. For A&A, enter the messaging number in international format and its dedicated outgoing SMS password. The A&A URL and mappings are supplied automatically.
4. For Custom HTTPS, enter the gateway username, password and final outbound HTTPS URL. In Advanced field mappings, match your gateway’s outgoing username, password, destination and message fields. The outgoing request is form-encoded; the gateway credentials determine the sending identity.
5. Set a success response prefix if your gateway requires one. With an empty prefix, an HTTP 2xx response means accepted. Acceptance does not confirm delivery to the recipient.
6. Select Save at the bottom of the page. The saved connection displays its Webhook URL. Select Copy URL and configure your incoming gateway with that entire URL.

The webhook belongs to the connection, not an individual number. Incoming messages are routed by their destination number to its enabled assignment. For A&A, set it as the number’s SMS Inbound target. For Custom HTTPS, your bridge posts to it after receiving and validating the carrier’s callback.

Custom HTTPS incoming message

With the default field mappings, send a JSON POST with Content-Type: application/json:

{
  "id": "message-12345",
  "from": "+15555550102",
  "to": "+15555550101",
  "text": "Your order is ready.",
  "timestamp": "2026-11-05T10:00:00Z"
}

Use + international numbers and a stable message ID. Retrying the same message must reuse its ID. If your gateway does not supply an ID, configure an ISO 8601 timestamp field so duplicate callbacks can be detected. The destination must match an enabled number assignment.

The generated URL contains a private token query parameter. Keep it intact, or send the same token in the X-SessionTalk-Webhook-Token header instead. Treat the token as a secret. Rotating it requires updating the sender’s callback settings.

Form-encoded POSTs are also accepted with the configured incoming field names. An HTTP 200 response with {"ok":true} acknowledges processing, including duplicate callbacks. It does not confirm app delivery or an enabled destination assignment. A 403 response means the webhook credential was rejected; 400 means the payload was invalid; 404 means the connection was not found or enabled.

These gateway connections accept text SMS, not MMS attachments or delivery status callbacks. For a service that also owns the inbox and media API, follow the direct service guide.

Connect and verify the app

Assign the messaging number to the exact SIP username and domain, then provide updated account provisioning. Test both directions and background notifications in the app. Messaging activity > Last received SMS confirms receipt at SessionCloud; it does not confirm that the phone received the message.

If the webhook URL is absent, save the provider connection, resolve any save error and reopen its settings. Customer-hosted service has no SessionCloud incoming webhook because that mode sends incoming carrier messages to your server.