Open-Source Ringover Connector
The Ringover connector enables easy and secure data synchronization between your application and your customers’ Ringover accounts through unified data models.
OAuth
The Ringover connector uses OAuth for secure authentication. When creating a connection, the required OAuth scopes are automatically configured based on your specific operations needs (e.g. genericContact::create
, genericUser::list
).
✓ Automatic token refresh handling
✓ Proactive insufficient permissions detection
View our step-by-step integration guide
Whitelabel
Supported
You can choose to provide your own set of clientId
and clientSecret
for this
connector from the Morph Cloud dashboard; allowing a fully whitelabled experience
for your end-customers.
Try a live demo of Ringover connection ✨
Live Demo
Select a connector below to experience our seamless authentication flow and see
how easy it is to connect third-party services.
Contact
The Ringover connector seamlessly integrates with our unified genericContact
model, enabling you to manage Contacts with rich data including firstName
, lastName
, phoneNumber
, email
and other key details
API Reference
GET | /resources/genericContact | List and Search Ringover Contacts |
GET | /resources/genericContact/:id | Retrieve a Ringover Contact |
POST | /resources/genericContact | Create a Ringover Contact |
PATCH | /resources/genericContact/:id | Update a Ringover Contact |
DEL | /resources/genericContact/:id | Delete a Ringover Contact |
Custom Fields
Supported
The Ringover connector supports our Field Mapping
feature, enabling you or your customers to seamlessly map Ringover Contact custom fields to the unified contact model. This allows for flexible data synchronization while maintaining data consistency across all connectors.
User
The Ringover connector seamlessly integrates with our unified genericUser
model, enabling you to manage Users with rich data including firstName
, lastName
, email
and other key details
API Reference
GET | /resources/genericUser | List and Search Ringover Users |
GET | /resources/genericUser/:id | Retrieve a Ringover User |
POST | /resources/genericUser | Create a Ringover User |
PATCH | /resources/genericUser/:id | Update a Ringover User |
DEL | /resources/genericUser/:id | Delete a Ringover User |
Custom Fields
Supported
The Ringover connector supports our Field Mapping
feature, enabling you or your customers to seamlessly map Ringover User custom fields to the unified user model. This allows for flexible data synchronization while maintaining data consistency across all connectors.
Workspace
The Ringover connector seamlessly integrates with our unified genericWorkspace
model, enabling you to manage Workspaces with rich data including name
and other key details
API Reference
GET | /resources/genericWorkspace | List and Search Ringover Workspaces |
GET | /resources/genericWorkspace/:id | Retrieve a Ringover Workspace |
POST | /resources/genericWorkspace | Create a Ringover Workspace |
PATCH | /resources/genericWorkspace/:id | Update a Ringover Workspace |
DEL | /resources/genericWorkspace/:id | Delete a Ringover Workspace |
Custom Fields
Supported
The Ringover connector supports our Field Mapping
feature, enabling you or your customers to seamlessly map Ringover Workspace custom fields to the unified workspace model. This allows for flexible data synchronization while maintaining data consistency across all connectors.
Call
The Ringover connector seamlessly integrates with our unified telephonyCall
model, enabling you to manage Calls with rich data including direction
, status
, startedAt
, answeredAt
, endedAt
and other key details
API Reference
GET | /resources/telephonyCall | List and Search Ringover Calls |
GET | /resources/telephonyCall/:id | Retrieve a Ringover Call |
POST | /resources/telephonyCall | Create a Ringover Call |
PATCH | /resources/telephonyCall/:id | Update a Ringover Call |
DEL | /resources/telephonyCall/:id | Delete a Ringover Call |
Custom Fields
Supported
The Ringover connector supports our Field Mapping
feature, enabling you or your customers to seamlessly map Ringover Call custom fields to the unified call model. This allows for flexible data synchronization while maintaining data consistency across all connectors.
Call Transcript
The Ringover connector seamlessly integrates with our unified telephonyCallTranscript
model, enabling you to manage Call Transcripts with rich data including call
, duration
, segments
, speakers
and other key details
API Reference
GET | /resources/telephonyCallTranscript | List and Search Ringover Call Transcripts |
GET | /resources/telephonyCallTranscript/:id | Retrieve a Ringover Call Transcript |
POST | /resources/telephonyCallTranscript | Create a Ringover Call Transcript |
PATCH | /resources/telephonyCallTranscript/:id | Update a Ringover Call Transcript |
DEL | /resources/telephonyCallTranscript/:id | Delete a Ringover Call Transcript |
Supported
Can’t find the unified model you need? The Ringover connector supports your own custom model.
Events Subscription
The Ringover connector supports real-time event subscriptions, allowing you to receive instant notifications when records are created, updated, or deleted. Below are the supported models and their corresponding triggers.
Models | Created | Updated | Deleted | API Reference |
---|---|---|---|---|
genericContact | ||||
genericUser | ||||
genericWorkspace | ||||
telephonyCall | ||||
telephonyCallTranscript |
Supported
The Ringover connector supports our Proxy Request
feature, allowing you to directly
call any endpoints from Ringover’s public API without needing to handle authentication.
Your customer’s token will be automatically set and refreshed as needed, enabling
quick implementation of custom connector behaviors. View API Reference.