...
User: every user of the MailUp service, regardless of whether they are paying for the service or taking advantage of the free trial period. Each User accepts the MailUp Terms of Use at the time they first log into the MailUp admin console, which is a required step to being be using the service.
MailUp Terms of Use: all the terms that regulate the use of the MailUp service. When such terms are changed, Users are asked to agree to them again when they log into the MailUp admin console
Application: a software program that leverages the MailUp API to access MailUp-powered services, making them available to other programs, such as Web sites, ecommerce e-commerce stores, CRM systems, etc.
Developer: the author of the application that uses the MailUp API. The Developer may or may not be a User. In the case of the MailUp REST API, the Developer is required to register the application in the MailUp system in order to obtain Application-specific access keys. Developers who are not Users may be provided with a "Developer Account", which gives access to the MailUp admin console free of charge, and with certain limitations.
...
The MailUp API
The MailUp API is actually a family of different APIs developed and updated through the years.
...
Web services based on the SOAP protocol, accessible at the following URLSURLs:
| Code Block | ||
|---|---|---|
| ||
https://wsvc.ss.mailup.it/ |
...
| Info |
|---|
| Support requests submitted through other channels, including social media, comments on the MailUp blog and online documentation (including this very Web site), and other resources, may not be answered to as they are not entered into the company's support ticket system. Make sure to open a support ticket by sending an email to the addresses listed above. |
...
This disclaimer applies to all Applications, including the "ready to use" ones that are listed on the MailUp Web site and the API online documentation.
Special warranties might be applicable apply to certain Applications: refer to the information provided with such Applications for details.
...
access to the services requires the use of a time-limited authentication token. You may authenticate using API-specific credentials (username= ‘a’ + account ID, e.g.. a23432; non-expiring password) or with admin console credentials (password expires after 180 days). The SOAP API does not enforce list access permissions that exist at the admin console level: all Users can access all llistslists, regardless of whether such Users were restricted to certain lists when accessing the service via the admin console. When using the “Import” SOAP Web service, based on the HTTP protocol, the User is aware of the risks involved in the transmissions of access credentials in a non-encrypted format, and that it is possibile possible to reduce any chances of unauthorized access by enforcing IP address validation in the API calls. [*]
...
Calls to the HTTP GET and POST API are performed without authentication. To minimize any abuse of the service, Developers are strongly encouraged to enforce the confirmed opt-in subscription method when adding subscribers to a list and to enforce IP address validation. These API apis are only available on the HTTP protocol. The User is aware of the risks involved in the transmissions of access credentials in a non-encrypted format, and that it is possibile possible to reduce any chances of unauthorized access by enforcing IP address validation in the API calls. MailUp is not responsible for unauthorized access to the services via these APIs when such security precautions have not been implemented.
...
Access to the REST API requires both (a) Application registration (the Application has been registered by the Developer); and (b) user authentication (when accessing the REST API, the Application must use certain specific credentials obtained when registering the Application). Users can view a list of Applications authorized to access their account and may revoke such authorization at any time. MailUp reserves the right to block access to the REST API to certain Applications that are found to be in violation of violate its Terms of Use. MailUp may enforce such block either globally to all Users that have authorized the Application, or individually for specific Users.
Application-based on the REST API may not store MailUp User access credentials in any way or form. They must instead store the access token obtained after the initial activation.
...
API | Features / Methods | Limitation |
http HTTP GET & POST | All | None |
SOAP API | CreateNewsletter SendNewsletterFast | Max 100 calls per day |
SendSingleNewsletter | Based on the level of service (bandwidth or messages per hour) purchased by the User [†] | |
SendNewsletter | Max 200 calls per day | |
SendDirectSMS SendSingleSMS | Max 10 calls per second | |
Other SOAP API methods | Max 5 calls per second | |
REST API | Transactional and personal emails | Based on the level of service (bandwidth or messages per hour) purchased by the User |
| Transactional SMS | Max 30 calls per second | |
| Stop/Delete sendings | Max 1 call every 30 seconds | |
Other REST API methods | Max 5 calls per second | |
SMTP+ | Transactional and personal emails | Based on the level of service (bandwidth or messages per hour) purchased by the User [‡] |
...
Certain APIs that are not being used by a User may be disabled in order to further minimize any risk of unauthorized use.
...
MailUp reserves the right to update its APIs - with or without prior notice - in order to achieve the following objectives.
...
Modifications to the API and information on new features (or versions, in the case of the REST API) that have become deprecated are registered in the API documentation. In some cases, updates might be sent to Users and Developers via email or another form of communication.
...
[*] IP address-based restrictions do not apply to the SOAP Web Services “MailUpSend”, “MailUpManage”, “MailUpReport” and to the JSONP Web services
[†] Without exceeding 100 calls per day if message type=HTML and 5,000 calls per day if message type=ID
[‡] Service limitation limitations are introduced when requests to send messages are sent at a speed that is far superior to the allocated bandwidth or messages per hour, with the result of a sending queue that exceeds 1,000,000 messages
[§] Unless all passwords associated with the MailUp accounts are reset
[**] If the feature cannot be accessed, please contact MailUp support