Set up Clearfly messaging
This integration is available in the portal as a pilot. Validate it with your provider account before customer rollout. A saved connection does not confirm live carrier delivery.
Open your BYO PBX project in Provisioning > Advanced > Messaging, enable SMS, and select this provider under Incoming and outgoing SMS.
- Select Clearfly in the SessionCloud messaging settings. Copy the webhook URL shown before saving credentials.
- In Clearfly, create an HTTPS Destination using that URL. Clearfly generates a REST account, REST token and Webhook token for the destination.
- Enter those three values in SessionCloud and use Save at the bottom of the page. Set each number’s messaging endpoint to that HTTPS Destination in Clearfly.
- Assign each number to its SIP account in SessionCloud, provide updated account provisioning, and test incoming and outgoing messages.
The same URL serves all numbers assigned to this connection. Copying the URL
does not create or enable a connection. Incoming JSON callbacks use HTTP POST
with Authorization: Bearer <Webhook token>. SessionCloud returns an empty
HTTP 200 after processing; repeated callbacks do not create duplicate messages.
Outgoing MMS supports one attachment, with attachment and caption together limited to 600 KB. Final delivery receipts are not implemented. If you regenerate credentials in the Clearfly portal , update the corresponding values in SessionCloud and save them.
Connect the app and test
Assign each messaging number to its user’s exact SIP username and domain, then provide updated authenticated provisioning or an account provisioning QR code. See Connect the app.
Test sending, receiving, duplicate callbacks, offline synchronization and background notifications. Check the carrier’s records before resending a message whose delivery is uncertain. Keep credentials and private webhook URLs out of screenshots and support messages.
Compare all messaging providers, or use the troubleshooting guide if messages fail.