03-17-2022, 01:54 PM
By MailerSend.com:
I would like to share an important update about our API.
From March 23rd at 12:00 UTC, we’ll be introducing a new daily quota to our API for all MailerSend accounts and an API Usage Policy as well.
This means there will be a maximum number of requests a single account can make within a 24 hour period. If you exceed the daily quota, the API or SMTP request will fail and return an HTTP 429 status code (but don’t worry—this can be easily avoided! See below).
The daily quota will:
I would like to share an important update about our API.
From March 23rd at 12:00 UTC, we’ll be introducing a new daily quota to our API for all MailerSend accounts and an API Usage Policy as well.
This means there will be a maximum number of requests a single account can make within a 24 hour period. If you exceed the daily quota, the API or SMTP request will fail and return an HTTP 429 status code (but don’t worry—this can be easily avoided! See below).
The daily quota will:
- Be applied at the account level. All API tokens and SMTP credentials of your account share the same quota
- Be based on your account plan. Premium and Enterprise plans have a higher daily quota than Free plan holders
- Count all API requests (valid or failed) and SMTP requests (authenticated only). We count an SMTP call when an SMTP client sends valid credentials and the DATA portion is sent through
- Be refreshed at midnight UTC
How can you avoid hitting the quota?
- Send your emails using the Bulk Email endpoint: you can send up to 35,000 in a single request
- Use webhooks instead of polling for changes
- Cache responses wherever possible instead of frequently making the same request
- If you’re sending marketing content, consider using a dedicated marketing emailing tool like MailerLite and using MailerSend for all transactional messaging.