APIs and integrations: connect Ediware to all your business tools
Your CRM holds your contacts. Your website collects leads. Your ERP manages your customers. And your emailing platform sends your campaigns.
If these tools do not talk to each other, you spend your time exporting files, re-importing them elsewhere, copying and pasting data between two interfaces. That is time lost, and a source of errors. Ediware's integrations connect your emailing platform to your existing ecosystem.
Synchronise your contacts with more than 1,000 applications through Zapier
Connecting a CRM to your emailing platform without writing a single line of code was still complicated a few years ago. You had to bring in a developer, go through export files, or cobble together in-house scripts. With Ediware's Zapier integration, it is a matter of minutes.
Synchronisation that works both ways
The integration is not limited to pushing data one way. Three triggers are available on your contact lists: contact added, modified, deleted. When a salesperson updates a record in the CRM, the contact is automatically updated in Ediware. And when a new prospect enters Ediware through a form, they flow back into your CRM. Two-way synchronisation. It is something many B-to-B clients check first, and rightly so.
Field mapping to keep your data clean
Each application structures its data its own way. A “Company” field in your CRM is not necessarily called the same thing in your emailing platform. Field mapping lets you match precisely the columns of the source application to the fields of your lists hosted in Ediware. Your data arrives in the right place, with no manual cleaning afterwards.
The features
- 1,000 applicationsconnected through Zapier, without writing a line of code
- Three triggerscontact added, modified, deleted
- Two-way synchronisationfrom the CRM to Ediware, and from Ediware to the CRM
Your business tools already compatible
Zapier bridges Ediware and more than 1,000 applications.
| Tool family | Compatible applications |
|---|---|
| CRM | Salesforce, HubSpot, Microsoft Dynamics, Sugar CRM, VTiger, Zendesk |
| Forms | Google Forms, Gravity Forms, Wufoo |
| Databases | MySQL, PostgreSQL, MongoDB, SQL Server, Oracle |
The list is long. If your tool is listed on Zapier, it can talk to Ediware.
Build emailing into your applications with no technical limits
Zapier covers most cases without writing code. But some projects call for more flexibility. Triggering a send from your business application, synchronising contacts in real time, driving your automation scenarios from your own interface. That is what Ediware's APIs are for.
REST API: manage contacts and campaigns from your tools
The REST API covers the common operations. Creating lists, inserting contacts in batches with automatic deduplication, sending personalised campaigns, retrieving statistics and form entries, handling unsubscribes. For agencies and resellers, it also allows sub-accounts to be managed with their own quotas and IP pools. It is the most used API for standard integrations.
SOAP API: drive the whole platform
The SOAP API gives access to everything. Complete campaign management, contacts with cleaning and search, detailed analytics, address checking against blacklists, driving automation scenarios. It is the API to prefer when the integration goes beyond the classic use cases, or for reseller architectures with sub-account management and credit allocation.
SMTP API: your transactional emails go through Ediware
Order confirmations, password resets, account notifications. Your transactional emails benefit from the same sending infrastructure as your marketing campaigns, with the same deliverability quality. The SMTP API fits into any application that sends email through the standard SMTP protocol. No specific library to install.
The rules
- REST APIlists, contacts in batches with deduplication, campaigns, statistics
- SOAP APIcampaigns, detailed analytics, blacklists, automation scenarios
- SMTP APItransactional emails through the standard SMTP protocol
Add SMS to your automated journeys without changing tools
Emailing does not cover every use case. For urgent messages, confirmations or follow-ups that have to be read within minutes, SMS remains unbeatable in terms of read rate. Ediware's SMS API lets you build SMS sending directly into your applications, with the same level of tracking as your email campaigns.
Schedulable and traceable sends
The API accepts up to 100 recipients per request. The sender name can be customised up to 11 characters, which lets your recipients identify the sender immediately. You keep control of the tracking of your sends.
Compliance with the legal rules built in natively
No marketing SMS between 8 p.m. and 8 a.m., nor on Sundays, nor on public holidays. Those are the rules in France, and the API builds them in directly. The SMS platform automatically blocks sending when you are outside the permitted windows. To go further on SMS possibilities, see our SMS platform.
What the webhook sends back
Click tracking is available through URL, and webhooks notify you in real time of each message's delivery.
Feed your lists straight from your WordPress forms
If your site runs on WordPress with Gravity Forms, the integration is even more direct. Form submissions automatically feed your contact lists in Ediware. A visitor fills in a form on your site, their data is recorded in the list of your choice. No export, no import, no manual handling.
It is the simplest connection between your site and your emailing platform. And if your needs go beyond the standard integrations, our team can develop custom connectors suited to your infrastructure.
Frequently asked questions about the API and integrations
Do you need technical skills to connect Ediware to my CRM?
No, if you go through Zapier. The integration is configured visually, without writing code. You select your CRM, you match the fields, and synchronisation starts. For deeper API integrations, a developer or an integrator will be needed.
Which API should I choose between REST and SOAP?
The REST API suits most cases: contact management, sending campaigns, retrieving statistics. The SOAP API is more complete and covers advanced features such as driving automation scenarios, detailed analytics and reseller sub-account management. The choice depends on how deep an integration you are aiming for.
Does Zapier synchronisation work both ways?
Yes. Three triggers are available on Ediware contact lists: added, modified and deleted. When a contact is created or modified in your CRM, it is updated in Ediware. And conversely, changes in Ediware can trigger actions in your other applications through Zapier.
Does the SMS API comply with French regulations?
Marketing SMS messages are not permitted between 8 p.m. and 8 a.m., nor on Sundays, nor on public holidays. The SMS platform handles these restrictions by preventing sends outside the permitted windows.
Can transactional emails be sent through Ediware?
The SMTP API lets you send your transactional emails through Ediware's infrastructure. Confirmations, notifications, password resets: these messages go through the same servers as your marketing campaigns, with the same deliverability quality.
Does the WordPress integration need a specific plugin?
The integration works with Gravity Forms, one of the most used form plugins on WordPress. Form submissions feed your Ediware contact lists directly, with no complex technical configuration.
Can Ediware develop a custom integration for my infrastructure?
When the standard connectors and Zapier are not enough, our technical team can develop custom connectors suited to your environment. It is the same team that develops the platform, and it knows every API and every module from the inside. A specific CRM connector, synchronisation with an ERP, a multi-site approval workflow: if it is technically feasible, we build it.
Make your tools talk to each other
Without changing your tools, without a heavy migration, and without friction.