Available solutions
- HTTP GET/POST (includes Subscription forms, that are based on the same methods)
- SOAP API
- REST API
- SMTP+ (SMTP Relay)
- FTP
- List+
- Other (Frontend reporting pages, Subscription forms)
You can develop your integration with MailUp by mixing the available solutions, taking advantage of the features they provide. Here below there is a comparison map between them.
Development can be done starting from scratch learning from available samples (see docs for each solution), or you can use the RubyGem
...
SUBSCRIPTIONS | HTTP, Forms | SOAP | REST | SMTP+ | FTP | List+ | Frontend |
---|---|---|---|---|---|---|---|
Import recipient (single) | 1 | 2 | |||||
Import of recipients (bulk) | 3 | ||||||
Bulk import limit (Mega Bytes or number of recipients) | MailUpImport : Multiple import by splitting in blocks, SendMessageNL: as FTP case | Multiple import by splitting in blocks, up to 5000 recipients 7 MB per block | 2 millions | 150000 | |||
Force optin of unsubscribed recipient (single) | ? | 2 | 2 | ||||
Force optin of unsubscribed recipients (bulk) | |||||||
Unsubscribe recipient (single) | 2 | ||||||
Unsubscribe recipient (bulk) | |||||||
Read personal data fields settings | |||||||
Update recipients' personal data fields | |||||||
Check recipient's subscription status | |||||||
Add to group (single) | 2 | ||||||
Add to group (bulk) | |||||||
Remove from group (single) | |||||||
Remove from group (bulk) | 4 |
...