46 results found

1. Individual Sender Address in Email API

   Based on a real-world ticket:

   We are using Mailjet as an SMTP relay for our domain, and the only valid sender address we have set up is our domain sender address "@mydomain.com". Now when emails are soft bounced, one could go to the Mailjet web portal and on the Stats page view which emails were not delivered and more importantly which individual sender sent the email (for example "harry@mydomain.com" taken from the email's From field). Therefore Harry could be informed that his email was not delivered.

   We have tried to automate the above process using the Mailjet API, but to do so we need to extract what was the value in the email's original From field. This is not made available anywhere in the Email API, and we also confirmed this through a ticket.

   Therefore it would be most helpful if somewhere in the message information, we could get this field, as otherwise, we have to manually download a CSV from the web portal and run a script that does the checking and sending. Having the From info in the API would allow us to completely automate this process.

   Thanks for your time and consideration.

   Based on a real-world ticket:

   We are using Mailjet as an SMTP relay for our domain, and the only valid sender address we have set up is our domain sender address "@mydomain.com". Now when emails are soft bounced, one could go to the Mailjet web portal and on the Stats page view which emails were not delivered and more importantly which individual sender sent the email (for example "harry@mydomain.com" taken from the email's From field). Therefore Harry could be informed that his email was not delivered.

   We have tried to automate the above process using the Mailjet API,… more

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Set DKIM key size with API

   DKIM Key Size Specification: The ability to specify the key size (1024, 2048, or 4096 bits) for the DKIM value of a sender domain via the API https://dev.mailjet.com/email/guides/senders-and-domains/#spf-and-dkim-validation

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Add Version to /eventcallbackurl to regroup by default the sended events

   Add "Version" to POST /eventcallbackurl (webhook creation), to regroup by default the sended events.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Automatically convert MJML templates added via API to html

   To be able to send an email using a template there must exist an HTML version of the template.
   When a template is created via API the HTML version must be provided in the API call (https://api.mailjet.com/v3/REST/template/{template_ID}/detailcontent).

   If an MJML template is provided to the API end-point, the API doesn't support creating the needed HTML version of the template that must exist for the template to possible to use.

   The only way to get an uploaded MJML template to work is to manually re-publish the API-created template via the web interface. This causes the email editor to automatically create an HTML version of the MJML content.

   Please add functionality that automatically generates the needed HTML version of the template, when an MJML template is uploaded via the API.

   To be able to send an email using a template there must exist an HTML version of the template.
   When a template is created via API the HTML version must be provided in the API call (https://api.mailjet.com/v3/REST/template/{template_ID}/detailcontent).

   If an MJML template is provided to the API end-point, the API doesn't support creating the needed HTML version of the template that must exist for the template to possible to use.

   The only way to get an uploaded MJML template to work is to manually re-publish the API-created template via the web interface. This causes the email editor to automatically… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Disable ip blocking for public cloud providers

   My application running in google app engine was unable to send emails for more than a day. All api invocations resulted in the connection being immediately closed from the mailjet side. The resulting ticket suggested it could be that the sending IP address was blocked owing to DOS prevention. But google cloud egress uses a shared pool of IP addresses so I have no influence over the ip address. Mailjet should accept the reality of the cloud situation and never block pooled ip addresses of reputable cloud providers. Mailjet is supposed to be a recommended service provider to google cloud customers.

   My application running in google app engine was unable to send emails for more than a day. All api invocations resulted in the connection being immediately closed from the mailjet side. The resulting ticket suggested it could be that the sending IP address was blocked owing to DOS prevention. But google cloud egress uses a shared pool of IP addresses so I have no influence over the ip address. Mailjet should accept the reality of the cloud situation and never block pooled ip addresses of reputable cloud providers. Mailjet is supposed to be a recommended service provider to google cloud… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. API secret Key - can be viewed without resetting

   It is a nightmare to be forced to reset api secret key every time we want to view it. It prompts us to stock the key on a excel sheet to be able to add it on new services ( since we cannot have multiple keys on a sub account for the moment). Why dont you allow to see the secret key after a double authentification for instance ? This would be totally safe and we wouldn't have ti reset it every time and change all ours services.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Wordpress plugin delete users as well as add

   Mailjet plugin for WordPress. When a user is deleted from WordPress can the plugin also delete them from the Mailjet contact list. Currently the syncing of existing and new WordPress users makes the semi useless. You already provide an API call to delete people from a Mailjet contact list, why can you not add a hook into WordPress so when a user is deleted it calls the API to delete the Mailjet contact. Thanks

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. header des mails non validés pour debuguer la provenance

   Bonjour,
   Lorsque un mail est envoyé avec une clé API de notre compte sans être validée, pouvoir avoir le header du mail en question pour pouvoir debuguer d'ou provient cet email.
   Merci

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. sendMail shall raise an error if template variables are missing

   Hi.

   we realized that the sendMail API has a problem. For instance if you are using a template that has 5 variables and your sendMail call includes just 4 values. Then sendMail yields SUCCESS but the mail will be listed as BLOCKED due to an error in the template later on (can be seen in the Mailjet stats). It would be cool if the sendMail function would return an error directly!

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. Resend an email via API

    Hi, could you please add a feature to resend an email via the email API ? It could be done by reusing the MessageId from the initial email to attempt the retry.

    This feature would be useful for automation processes, for example to resend emails when the recipient no longer has access to the initial email

    5 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Email API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Modification du mail "une adresse d'expédition..."

    Pourriez-vous modifier le contenu du mail "une adresse d'expédition non validée a été utilisée sur votre compte" et y ajouter le nom du sous-compte concerné (en plus de la clé api principale)?

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Email API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Unify Versions fo SendAPI and Contact Management API

    I am currently using the Contact Management API to allow subscriptions via our Website, and also sending a 2-step Opt-In 'confirmation' email as one of the processes.

    I can't use the same API Client object for Send and Contact Management operations currently as API v3.1 only works with Send API endpoints (any Contact Management endpoints just result in a 404) and Contact Management still uses V3, Send API operations are significantly different from the documentation in v3, to the extent where the v3.1 Examples don't work with the v3 endpoints.

    It would be greatly more convenient if v3.1 had a unified Send API and Contact Management API

    I am currently using the Contact Management API to allow subscriptions via our Website, and also sending a 2-step Opt-In 'confirmation' email as one of the processes.

    I can't use the same API Client object for Send and Contact Management operations currently as API v3.1 only works with Send API endpoints (any Contact Management endpoints just result in a 404) and Contact Management still uses V3, Send API operations are significantly different from the documentation in v3, to the extent where the v3.1 Examples don't work with the v3 endpoints.

    It would be greatly more convenient if v3.1 had a… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Email API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Add an api that allow to retrieve template content after variable interpolation

    Add an api that allow to retrieve template content after variable interpolation because we need to store the resulting email on a webserver

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Email API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Allow to retrieve variables from a template

    Hello,
    We use a template system and send variables from a Java backend. To make it dynamic, we retrieve the template and analyze the detailcontent: Text-part to extract the variables, and then send them. An improvement would be to directly retrieve the variables.
    What I would like is to be able to retrieve the variables used inside a template email, for instance when using the java mailjet client, I would like a new enum called Variables and do somethind like that:

    public class TemplateDetailcontent {

    public static Resource resource = new Resource("template", "detailcontent", ApiVersion.V3, ApiAuthenticationType.Basic);
    
    public static String TEXTPART = "Text-part";
    public static String HTMLPART = "Html-part";
    public static String MJMLCONTENT = "MJMLContent";
    public static String HEADERS = "Headers";
    
       // ADDING new field to retrieve variables
        public static String VARIABLES= "Variables";
    

    }

    For now I am parsing Text -part and use the folllowing regex to retrieve variables:

    private List<String> getTemplateVars(long templateId) throws MailjetException {
    List<String> variables = new ArrayList<>();
    // Retrieve template
    MailjetRequest reqTemplate= new MailjetRequest(TemplateDetailcontent.resource, templateId);
    MailjetResponse respTemplate = getMailClient(this.apiKey, this.apiSecretKey).get(reqTemplate);
    if (respTemplate.getStatus() == 200) {
    JSONArray jArr = respTemplate.getData();
    if (jArr.length() > 0) {
    JSONObject jObj = jArr.getJSONObject(0);
    String textPart = jObj.getString(TemplateDetailcontent.TEXTPART);
    Pattern pattern = Pattern.compile("\{\{var:(\w+)(?::\w+)?}}");
    Matcher matcher = pattern.matcher(textPart);
    while (matcher.find()) {
    variables.add(matcher.group(1));
    }
    }
    }
    log.info("vars: {}", variables);
    return variables;
    }

    Hello,
    We use a template system and send variables from a Java backend. To make it dynamic, we retrieve the template and analyze the detailcontent: Text-part to extract the variables, and then send them. An improvement would be to directly retrieve the variables.
    What I would like is to be able to retrieve the variables used inside a template email, for instance when using the java mailjet client, I would like a new enum called Variables and do somethind like that:

    public class TemplateDetailcontent {

    public static Resource resource = new Resource("template", "detailcontent", ApiVersion.V3, ApiAuthenticationType.Basic);
    
    public static String TEXTPART =

    … more
    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Email API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. Add a filter to fetch new and updated contact and contactdata entities

    To simplify ETL processed we need just recently added and updated contacts and contactdata. Current API endpoint is not offering filter for this.

    Comparable with bouncestatistics: FromTS and ToTs query parameters.

    Now we need to refresh data daily and the amount of data being moved is kind of huge.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Email API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Améliorer gestion d'erreur expéditeur

    Bonjour,
    n'est-il pas possible de changer le retour de votre API lorsque l'on tente d'envoyer un mail avec un expéditeur non validé? J'ai récemment eu un souci lié à un expéditeur autorisé uniquement sur le compte principal mais pas sur un sous compte (cf ticket #2434150) et j'avoue que le retour API nous a vraiment induit en erreur. Pour cause, dans ce cas, l'API nous transmet un succès et un id de message comme si tout était OK, sauf que malheureusement, l'envoie n'as pas fonctionné et l'id renvoie une 404 lorsqu'on tente de faire un get ?
    Ce correctif serait vraiment utile pour nous, car nous utilisons les retours dans notre système pour détecter si l'envoie à marcher ou non et en l'état, cella empêche donc notre système de détecter l'erreur ce qui rend notre système moins fiable.

    Merci beaucoup,
    Cordialement

    Bonjour,
    n'est-il pas possible de changer le retour de votre API lorsque l'on tente d'envoyer un mail avec un expéditeur non validé? J'ai récemment eu un souci lié à un expéditeur autorisé uniquement sur le compte principal mais pas sur un sous compte (cf ticket #2434150) et j'avoue que le retour API nous a vraiment induit en erreur. Pour cause, dans ce cas, l'API nous transmet un succès et un id de message comme si tout était OK, sauf que malheureusement, l'envoie n'as pas fonctionné et l'id renvoie une 404 lorsqu'on tente de faire un get ?
    Ce correctif serait… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Email API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Test the render of email with templating language

    Add to the return of the sandbox email sending API the email that would have been sent to test the working of the templating language conditions.

    if it's too complicated, can you open your internal API https://app.mailjet.com/passport/ipa/render to test the templating language

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Email API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. récupérer expéditeur exact via API

    Avec l'API, le path 'https://api.mailjet.com/v3/REST/message' permet de récupérer des informations sur les messages envoyés.
    Nous pouvons récupérer notamment, l'attribut "SenderID" qui donne l'identifiant d'un expéditeur validé. Nous avons validé le nom de domaine @mondomaine.com (par exemple) donc on sait que SenderID correspondant à @domaine.com cependant j'aimerai savoir qui est l'expéditeur exact (toto@domaine.com, titi@domaine.com, ...).
    L'information doit bien être stockée quelque part puisque quand on fait un export CSV à partir de Mailjet cette information est bien disponible.

    ENGLISH
    With the API, the path 'https://api.mailjet.com/v3/REST/message' allows us to retrieve information about the messages sent.
    In particular, we can retrieve the "SenderID" attribute which gives the identifier of a validated sender. We have validated the domain name @domain.com (for example) so we know that SenderID corresponds to @domain.com however I would like to know who is the exact sender (toto@domaine.com, titi@domaine.com, ...).
    The information must be stored somewhere because when you do a CSV export from Mailjet this information is available.

    Avec l'API, le path 'https://api.mailjet.com/v3/REST/message' permet de récupérer des informations sur les messages envoyés.
    Nous pouvons récupérer notamment, l'attribut "SenderID" qui donne l'identifiant d'un expéditeur validé. Nous avons validé le nom de domaine @mondomaine.com (par exemple) donc on sait que SenderID correspondant à @domaine.com cependant j'aimerai savoir qui est l'expéditeur exact (toto@domaine.com, titi@domaine.com, ...).
    L'information doit bien être stockée quelque part puisque quand on fait un export CSV à partir de Mailjet cette information est bien disponible.

    ENGLISH
    With the API, the path 'https://api.mailjet.com/v3/REST/message' allows us to retrieve information about the messages sent.… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Email API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Awful API documentation and examples

    API documentation is atrocious. Example given for sending a basic email does not work, gives a 400 error message stating that "At least FromEmail or Sender must be provided" when following all steps provided. No further details about this error in the documentation. Price was a good draw, but API like this will have us going to another provider.

    7 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Email API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. Sent email summary report

    Is it possible to have an email sent to us with a summary of the previous days sent emails, we use the service to send order emails and if one gets soft bounced or other errors we are not aware of it. It would be good if we can have an email summary sent to us each day so we can look out for issues, so it says x% were soft bounced, x% blocked etc...

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Email API  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close