Page tree

Versions Compared


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

2018-10 Breaking changes

  • REST API v. 1.0, mainly used by previous version of the Salesforce connector, was discontinued on Sep 30th. All the customers using it have been informed in advance and invited to migrate their client or to update their Saleforce connector

  • Unused developer accounts will be discontinued (and deleted) starting from Sep 30th. Account owners have been informed in advance, some of them asked to keep their accounts. All the requests have been accepted and this breaking change was a chance for us to link the owner of a developer account to its production account.

  • Since the REST API has finally covered all the feature set of the SOAP API, we can set the REST as the only featured API. Due to the large number of customers using it, we cannot deprecate the SOAP API. We simply mark it as "no longer recommended to use if you are starting a new project or planning to extend an existing one"

  • Access tokens must now be refreshed every hour either for SOAP or REST (it was 15' for the REST API). As the SOAP API is now using the same Authorization methods as the REST API, the expiration of the validity time is now the only way to dismiss a token and to deny the access. Any call to “logout” methods has become useless.

2018-10 Import by file, content update, privacy settings and global search

  • You can now upload a file via FTP and pass the filename as a parameter to the import REST API for immediate import. This feature allows to overcome the size limits we have had so far when trying to pass tons on recipients in the request body. With this extension, the MailUp REST API covers the last missing method that resulted when comparing REST and SOAP. More details here.

  • Access to the MailUp REST API resources has an improved algorithm for rate limiting. Even though the threshold of 5 calls/s is unchanged, clients exceeding this limit may experience a slightly different error rate. 

  • The “global search” of recipients can now be performed by ID, email or mobile number. A single API call returns both the personal data fields and the subscription status on all the lists and channels. More details here.

  • According to the privacy settings introduced with GDPR, you can now use also REST API to fully remove a recipient or to disable tracking for it. More details here.

  • An external content can now be pushed to MailUp using REST API and then used for automated campaigns or to be easily dragged into your messages. More details here.

2018-03 OAuth 2.0 authorization module reviewed