...
MailUp reserves the right to reduce or suspend the service when the following thresholds have been exceeded.
API | Features / Methods | Limitation |
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 [‡] |
Error handling and logging
...
Support is limited to the use of the API and does not cover proper development of any Application, including error handling and logging, unless otherwise agreed in writing.
Throttling limitations
Here below the throttling limitations:
Disabling of certain APIs
Certain APIs that are not being used by a User may be disabed disabled in order to further minimize any risk of unauthorized use.
API | Features / Methods | How to disable it |
HTTP GET & POST API | Subscribe.aspx | Cannot be disabled |
Other pages (e.g.. xmlSubscribe.aspx) | Via admin console (Settings > Account settings > Developer's corner > Web services > FrontEnd) | |
SOAP API | MailUpImport | Via admin console (Settings > Account settings > Developer's corner > Web services > MailUpImport) |
Other SOAP API methods | Cannot be disabled [§] | |
REST API | All | Revoke Application authorization in the admin console [**] |
SMTP+ | All | Remove all SMTP+ users |
Updates
MailUp reserves the right to update its APIs - with or without prior notice - in order to achieve the following objectives.
- SOAP API, JSONP, HTTP GET & POST API: backward compatibility, implemenetation implementation of new features, increase in security
- REST API: supports versioning and multiple versions can be active at the same time. An older version should be considered deprecated 6 months after the next version was released.
- SMTP+: maintain compliance with the SMTP protocol specifications
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 other another form of communication.
Footnotes
...