API INTEGRATION

Calls, SMS and CRM connected over REST API — a 3CX Cloud LT solution

Over REST API, 3CX Cloud LT connects to your CRM, ERP or accounting system: you start a call with one click, an incoming call opens the customer card on screen, and call recordings and history land in your system. SMS is sent and received the same way, and events come back through webhooks.

200 OKPOST/api/callsCall in progressAnswerTransferEndCRM CARDhistory and recordingsREST API
CRM and ERP

How are calls linked to a CRM or ERP?

An incoming call opens the customer card, every conversation is logged together with the recording and history, and an outgoing call starts from that same card. This runs on a universal integration module fitted to your CRM or ERP.

CRM AND ERPCustomer callsCustomer cardappears before the phone is picked upLoggedinto customer history
  • Customer card on screen

    The agent sees who is calling before picking up the phone.

  • Calls are logged

    Every conversation is written into the customer history automatically.

  • Universal module

    One module fits your system: amoCRM, Bitrix24, HubSpot, Dynamics 365, Salesforce, Zendesk, Zoho and others.

  • Events, history and recording

    The module gives you call events, history and the option to download the recording.

Call control

What can be controlled over the call API?

A call can be started, answered, transferred, put on hold and ended from your system. Call events plus active call and agent status information are passed along with it.

CALL APIPOST/api/callsOne request from your systemCall in progressAnswerTransferHoldEndCall events come back to your system
  • Starting a call

    An outgoing call starts from the CRM or ERP with a single request.

  • Control during the call

    Answer, transfer, hold and end.

  • Events in both directions

    Incoming and outgoing call events are passed to your system.

  • Active calls and agents

    See the calls in progress and agent statuses.

SMS over API

What does the SMS API allow?

Messages are sent and received over the same API: single, recurring or bulk from Excel or CSV with variables. The delivery report comes back.

  • Sending and receiving

    Outgoing SMS is initiated, incoming messages are passed to your system.

  • Bulk sending

    A list from Excel or CSV with variables for each recipient.

  • Recurring messages

    The message goes out on a schedule set in advance.

  • Delivery reports

    See which messages reached the recipient and which did not.

Call recording

How does the call recording reach the CRM?

When the call ends, the recording and history are passed to your CRM or ERP over the same REST API. They attach to that customer record, so there is no need to search the phone system.

CALL RECORDINGCall endedCall recordingCall historyCUSTOMER CARDThe recording attaches to the customer card
  • On the customer card

    The recording goes to the customer you spoke with, not into a separate list.

  • History included

    Not only the recording is passed, but the call history as well.

  • No searching in the phone system

    The agent opens the customer card and finds the recording right there.

  • The same REST API

    Passed over HTTPS and JSON with Bearer authentication; events through webhooks.

Automation

What can be automated over the API?

Automated calls and SMS from your list or schedule, post-call surveys, and their scores passed into your system together with reports.

  • Automated calls and SMS

    Notifications go out by project and planned schedule.

  • List from Excel or CSV

    Data can be uploaded as a file or taken from the CRM.

  • Post-call surveys

    Service quality rating by call or SMS.

  • Scores over the API

    Results are passed to your system and shown in reports.

Equipment and access

Can equipment and access be controlled over the API?

Yes. The same path controls barriers, gates, door phones and doors, and entry can be confirmed with a QR code — to a gym, for example. The action runs from Android, iOS, Windows or a browser.

EQUIPMENT CONTROLOpenFrom phone or browserREST APIBarrieropens on commandObjects on the GPS map
ACCESS CONTROLDoor phone and doorsREST APIAccess by QR code
  • Barriers and gates

    A barrier or gate opens on command from the app or a browser.

  • Door phones and doors

    Doors are unlocked from the app or by a call.

  • Access by QR code

    Entry — to a gym, for example — is confirmed by scanning the code.

  • GPS map and events

    Objects are shown on the map and events are passed through webhooks.

Frequently asked questions

Which API does 3CX Cloud LT use?

REST Full API: HTTPS, JSON and Bearer authentication. Webhooks are used for events — the data arrives at once rather than on a polling schedule.

Can a call be started straight from the CRM?

Yes. An outgoing call is initiated with a single API request from a CRM, ERP or another system, and the call can be answered, transferred, held and ended the same way.

What happens when a customer calls?

The call is linked to the customer record automatically and their card appears on the agent’s screen, while the call itself is logged in your system.

Which CRM systems do you connect to?

amoCRM, Bitrix24, HubSpot, Microsoft Dynamics 365, Microsoft Office 365, Salesforce, Zendesk, Zoho and others. If your system is not on the list, the integration is built on its API.

Can SMS be sent over the API?

Yes: single, recurring and bulk messages from Excel or CSV with variables. Incoming SMS is passed to your system and delivery reports come back.

Does the API suit non-telephony equipment?

Yes. The same API controls barriers, gates, door phones and doors, and entry can be confirmed with a QR code — to a gym, for example. Objects are visible on the GPS map from Android, iOS, Windows or a browser.

Next step

Let’s look at your case

Write to us which system you are connecting and what data you need from it — we will tell you what can really be done with 3CX Cloud LT.

Ask us