The case "The message was sent but the statistics are incorrect due to an error" with Application Code = 301 now returns HTTP 200 instead of HTTP 500. More details here
REST API v. 1.0, mainly used by the previous version of the Salesforce connector, was discontinued on Sep 30th
Unused developer accounts were discontinued on Sep 30th
The SOAP API is now marked as "no longer recommended to use if you are starting a new project or planning to extend an existing one". REST API covers the feature set of the SOAP API.
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 us 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.
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.
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.
Error code HTTP 429 is now returned instead of HTTP 403 when the rate limit is exceeded. As before, clients have to retry later when this error type occurs
The email alert at the very first access to API is no more sent to the technical contacts of the accessed MailUp account
The token type “MailUp” is no longer supported on v.1.1 of MailUp REST API. Clients using this value have to be migrated to the OAuth 2.0 flow using the “Bearer” token
Great news for those that use MailUp to send transactional emails.
Lots of new features and substantial performance improvements.
POST Console/List/{ListID}/Recipient?ConfirmEmail=true |
Adds a new subscriber to the specified list with the "Confirmed Optin" option turned on, which is an email marketing best practice. The recipient is added as "pending" and a confirmation request email is automatically sent.
POST Console/Group/{GroupID}/Recipient?ConfirmEmail=true |
Same as above, but the recipient is both (a) added to the specified group and (b) subscribed to the list that the specified group belongs to.
POST Console/List/{ListID}/Recipients?ConfirmEmail=true |
Adds a list of subscribers to the specified list with the "Confirmed Optin" option turned on. Recipients are added as "pending" and a confirmation request email is queued but not automatically sent
POST Console/Group/{GroupID}/Recipients?ConfirmEmail=true |
Same as above, but recipients are both (a) added to a specified group and (b) subscribed to the list that the specified group belongs to.
GET Console/Import/{id_import}/Sending |
Gets the ID of the mailing that has been created in the system when adding recipients with the "Confirmed Optin" option set as 'true'. The mailing refers to the subscription confirmation request message.
POST Console/Email/Sendings/{id_Sending}/Immediate |
Schedules a mailing for immediate sending (i.e. send as soon as possible).
POST Console/Email/Sendings/{id_Sending}/Deferred |
Sets up a mailing for scheduled delivery (i.e. send at specified date and time)
POST Console/List/{ListID}/Recipients?importType='asOptout' |
Allows you to "import as unsubscribed" a list of specified recipients. Please note that this important task will affect current subscribers, forcing their subscription status to "unsubscribed".
GET Console/Email/Sendings/Immediate |
Retrieves from the sending queue the list of email messages that are currently queued up for "immediate sending".
GET Console/Email/Sendings/Deferred |
Retrieves from the sending queue the list of email messages that are currently scheduled for deferred delivery.
GET Console/Email/Sendings/Undefined |
Retrieves from the sending queue the list of messages that are neither "scheduled" nor queued up for "immediate sending". This is a "limbo" state that messages are placed into when they are removed from the queue either manually or because there was an issue.
GET Console/Email/Sending/{id_Sending}/Deferred |
Retrieves the earliest date to schedule the given sending task.
POST Console/List/{id_List}/Email/{id_Message}/Send?datetime='1994-11-05T13:15:30Z' |
Allows you to schedule a specific message for deferred delivery. Make sure to use the UTC zone when specifying the date and time.
GET - Console/List/{id_List}/Recipient/{id_Recipient}/Groups |
Retrieves the list of groups to which the specified recipient has been assigned
GET - Console/List/{id_List}/Archived/Emails |
Retrieves the list of the archived emails in the specified list
Version 1.1 has been officially released (see changelog) and has been removed. Online documentation is now updated.
We're already at work on a new version of the REST API.
Version 1.0 of the MailUp REST API is already being used in some integrations, including the MailUp App for Salesforce. We are still optimizing it for big volumes of data (this is the main reason for the tag) and, at the same time, we are working to introduce additional filtering, paging, and ordering capabilities in version "1.1".
Some changes in the API related to these new features will affect backward compatibility, and therefore version 1.1 will be released with a different endpoint.
The expected release date for v1.1 is sometime in September 2013. When version 1.1 is released:
We don't expect that you will be frequently asked to switch endpoint: please consider this as a rare case that is due to the young age of the MailUp REST API project. Future improvements are expected to be applied to version 1.1 without backward compatibility problems.
Here is a list of new features that will be available in v1.1:
The MailUp REST API documentation is now public.