Our Engaging Networks Services (ENS) cover three types of service to solve different integration requirements.
1. Non-sensitive services (public)
These services are useful for bulk statistics, social proofing (e.g. roll calls) and certain non-sensitive aggregate data representations. For example, it is the service that our display widgets use.
As the service does not return any sensitive supporter data, it can be used ‘on the page’ with javascript.
Read more about data calls you can make
2. Bulk API services (private)
These are designed for the regular bulk import and export of data, outside of the Engaging Networks dashboard. They are heavy duty, and a lot of information is returned or required. These services are used for batches of data – they are not practical for single supporter updates or adding a single transaction. Examples of use:
- CRM integrations where there are large amounts of supporter updates or creations,
- Transactional import of offline donations or data collection
- Import of CRM segments defined externally to be emailed through Engaging Networks
These are accessed via the private token which must be kept secured. With the Export API, you will get every type of transaction returned from the past 32 days unless you have requested only a certain campaign type or have adjusted your export API settings or are using an Export Group. Please refer to the ‘Transactional Data format’ as this is the core of understanding how ‘supporter events’ are represented.
More information:
URLs used:
- https://us.engagingnetworks.app/ea-dataservice/export.jsp
- https://ca.engagingnetworks.app/ea-dataservice/import.jsp
3. REST services (private)
REST services are programmatically accessed outside of the system. They need a special API user token which must be kept secured. They are useful when integrating external forms or apps with Engaging Networks, when single transactions or updates will occur (i.e. not in bulk).
This service can CRUD (Create, Read, Update and Delete) a supporter remotely and post into donation, petition and other campaign pages.
The session needs to be authenticated first with the API User’s key, which will return a token to be used in subsequent calls. The token lasts for approximately one hour.
Read more about REST services here
Third-party integrations
CRM integrations
There are some CRM integrations available:
- Salesforce – more here
- Raiser’s Edge – JMG Solutions and Omatic provide plugins