Feature Requests

I am concerned about the lack of an idempotency key in your API, which is a common technique to prevent issues if a developer makes a mistake. Without it, there's a risk of spamming clients, leading to dissatisfaction and potential budget issues. Implementing an idempotency key would help mitigate these risks and improve reliability.

All of our emails seem to be routed through Europe (Netherlands and Lithuania) This is causing a large chunk of them to get blocked as I deal with municipal government agencies in the US exclusively. mail021.mlsend.com [185.225.161.21] MailerSend [212.11.79.129 - Netherlands]

I noticed that the MAILERSEND.EMAIL .MESSAGE.SINGLE(MESSAGE_ID) endpoint doesn't include recipient information in its response. It would be beneficial if this endpoint could return complete sender information for individual emails, similar to the ACTIVITY METHOD. This enhancement would simplify the process of tracing emails and improve overall efficiency.

We would like to be able to use your API to filter activity by recipient email address. This can be done using your dashboard but the API seems to be lacking this feature. Webhooks alternative was provided but for regulatory reasons, we need to keep a record of communications to our clients so MailerSend is ideal for this and keeping this information off our internal systems would be perfect. However, we would need the API integration so that lookups can be done between our internal platform and yours.

I need a way to preview email templates fully via API services. Currently, the API only provides a screenshot of the template, which is insufficient for my needs. Having an endpoint that allows for a complete preview of the templates would greatly enhance my workflow and efficiency.

I need the ability to schedule emails to be sent more than 72 hours in advance, such as a week or even a month later. This feature would greatly enhance my ability to plan and manage email communications effectively.

I encountered an issue where personalization values can only be set for recipients in the 'To' field, not for those in the CC or BCC fields. This limitation requires me to include everyone in the 'To' field, which is not ideal. It would be beneficial if personalization could be extended to CC and BCC recipients, allowing for more flexibility in email customization.

I noticed that while MailerSend supports S/MIME, there is no documentation on how to attach a signature certificate to emails, especially for bulk mailings. It would be beneficial to have a short instruction or guide on this process to ensure proper implementation.

When there is an error in a template or due to null data variables, MailerSend still sends the email, displaying variable names without rendering them. It would be helpful to have a feature that prevents sending emails in such cases and instead provides an error response.

I often need to send images, such as customer logos, dynamically in our communications. It would be beneficial if I could send an image link in the API call, allowing the image to be loaded remotely, rather than uploading it each time.