Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


In addition, we have a JSON framework for CRM (and other systems) integrations. We are still in the process of documenting it, but I’m happy to help providing informatoin here. Briefly, your CRM system needs to implement have HTTP API endpoints to listen to the requests from a Ringotel server. Ringotel will make requests on the different stages of the workflow, for example, when setting up the integration in the portal, creating a contact, on incoming/outgoing call, etc. The endpoints and their format depends on what functionality and data you expect to recive in this integration.


The integration has the following prerequisites:

  • Your web service CRM needs to be able to receive and respond to HTTPS requests with JSON content.

  • Your web service CRM needs to be able to authorize requests from a Ringotel server using Basic, Bearer, or OAuth2 method.

  • Your web service CRM need to be able to accept and return data in the predefined format.

  • Your web service CRM should respond to the authentication requests from Ringotel with the stadard 200 OK or 403 Forbidden HTTP codes.


You can implement the following HTTPS endpoints on your web service where Ringotel will send requests as a part of the workflow.Currently, Ringotel supports the following workflow:

Users (required)

Must provide the list of CRM users to map with the Ringotel users. Each user needs to have unique identifier (ID).


Uploads and attaches a call recording file to a specific activity (identified by ID).

The list of endpoints can vary depending on the features you need.


Lastly, below you Below you can find a JSON document where you can find the examples of with a CRM integration (with some details obscured)example. Should you have any questions, please don't hesitate to contact us at

View file