| Note |
|---|
The content of this page applies to all the methods of MailUp REST API except for the Transactional APIs, which do not use OAUTH 2.0 |
| Note | ||
|---|---|---|
| ||
From March 2018, MailUp has introduced the HTTP 429 (Too many requests) status code; it replaces the old 403 (Forbidden) status code. |
Before you start
MailUp REST API follows OAuth 2.0 specification and authorizes only the applications that specify a pair of valid access keys ("Client ID" and "Client Secret") in the authentication process.
...
- HTTP 400 (Bad request): request malformed, or missing one or more parameters.
- HTTP 401 (Unauthorized): token expired, revoked, malformed or invalid for any other reason.
- HTTP 403 (Forbidden): the application is requesting a resource which is not in the scope of the impersonated user. This error code
- HTTP 429 (Too many requests): it is returned also in case of too many requests per second on a single API resource.
- HTTP 500 (Internal error): returned in case of any resource server internal problem.
...