3CX SMS: send and receive business texts in 3CX with everymessage

How the integration works

3CX sends each outgoing text to everymessage as a simple request with your API key. We send it to the mobile networks and track delivery. When the message is delivered, or a customer replies to your number, we post it straight back to your 3CX system, which shows it in the right conversation.

What you need

• A 3CX system that supports SMS through a generic provider
• An everymessage account with an API key
• An SMS-enabled number from everymessage for customers to text and reply to, set up in 3CX
• Your 3CX webhook URL, which 3CX shows when you add the SMS provider

Setting it up

1. Get your API key. We provide your everymessage API username and password. Your API key is username:password, Base64-encoded.
2. Add the SMS provider in 3CX. In your 3CX SMS settings, choose the generic provider, enter the everymessage messages URL below, and paste in your API key.
3. Add your number. Set up your everymessage SMS number in 3CX and choose which users or queues handle its texts.
4. Send us your webhook URL. Copy the webhook URL 3CX shows for the provider and send it to us. We set it against your number in the 3CX / Yeastar (PBX) format, for both replies and delivery reports.
5. Test. Send a text from 3CX, check it arrives and shows as delivered, then reply from the mobile and check the reply appears in 3CX.

API reference

You don’t need this to use 3CX, but it shows exactly what 3CX and everymessage exchange, which helps if you’re testing or troubleshooting. The full reference, with code examples, is in our developer docs: Phone systems (PBX) API.

Send a message

3CX posts each text as JSON, with your API key as a Bearer token. from, to and text are all required, and numbers are in E.164 format.

curl -X POST "https://api.everymessage.com/v1/pbx/messages" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{"from": "+447700900456", "to": "+447700900123", "text": "Your engineer is on the way."}'

Errors return a JSON errors list with a code, title and detail; the codes are listed under common problems below. A successful request returns HTTP 200 with the message details. The id is the everymessage message id, which 3CX uses to match the delivery report:

{
  "data": {
    "record_type": "message",
    "direction": "outbound",
    "id": "123456",
    "type": "SMS",
    "from": { "phone_number": "+447700900456" },
    "to": [ { "phone_number": "+447700900123", "status": "queued" } ],
    "text": "Your engineer is on the way.",
    "encoding": "GSM-7",
    "parts": 1
  }
}

Replies

Customer replies are posted to your 3CX webhook as a message.received event:

{
  "data": {
    "event_type": "message.received",
    "record_type": "event",
    "payload": {
      "id": "123789",
      "direction": "inbound",
      "type": "SMS",
      "from": { "phone_number": "+447700900123" },
      "to": [ { "phone_number": "+447700900456" } ],
      "text": "Thanks, see you soon",
      "received_at": "2026-10-13T09:15:04.511Z"
    }
  }
}

Delivery reports

When a message is delivered or fails, a message.finalized event is posted to the same webhook. payload.id is the id returned when the message was sent, and to[].status is delivered or delivery_failed.

Common problems and fixes

Why use everymessage for 3CX SMS

Using Yeastar? The same everymessage PBX API works with it too: see Yeastar SMS. Using a different phone or contact centre platform? See NetSapiens SMS, Amazon Connect and every other way to connect on our Business SMS page.

Frequently asked questions