43 results found

1. 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

2. 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

3. pipeline

   I would like Mailjet to be able to talk to our CRM software, Pipeline. Our contact list is dynamic and changes on a daily basis. If I could somehow mass flag people in pipeline based on their status in Mailjet (high risk, low risk, hard bounce, soft bounce, etc) that would be extremely helpful so that I can exclude these contacts when uploading a new list.

   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

4. Be notified after ip denied

   It could be cool to be notified when our address ip is denied with the information of the reason and time of the denial.

   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

5. Webhook weiteres Feld - Webhook further field

   Hallo, könnten sie bitte bei den Wehooks ein Feld
   from: Absender der Email
   hinzufügen.
   Bisher gibt es nur den Empfänger:
   email: email address of recipient triggering the event
   und
   mjcontactid: internal Mailjet contact ID
   Dies ist aber nicht der wirkliche Absender, da es auch *@domain.de sein kann.
   Der tatsächliche Absernder ist sehr wichtig um Mail entsprechend zu bearbeiten.
   Danke.

   Hello, could you please add to the wehooks a field
   from: Sender of the email
   to be added.
   So far there is only the recipient:
   email: email address of recipient triggering the event
   and
   mjcontactid: internal Mailjet contact ID
   But this is not the real sender, because it can also be *@domain.de.
   The real sender is very important to process mail accordingly.

   Hallo, könnten sie bitte bei den Wehooks ein Feld
   from: Absender der Email
   hinzufügen.
   Bisher gibt es nur den Empfänger:
   email: email address of recipient triggering the event
   und
   mjcontactid: internal Mailjet contact ID
   Dies ist aber nicht der wirkliche Absender, da es auch *@domain.de sein kann.
   Der tatsächliche Absernder ist sehr wichtig um Mail entsprechend zu bearbeiten.
   Danke.

   Hello, could you please add to the wehooks a field
   from: Sender of the email
   to be added.
   So far there is only the recipient:
   email: email address of recipient triggering the event
   and
   mjcontactid: internal Mailjet… 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. Double Opt In API

   I would like to have an API end point that could be used to trigger a double opt in. Meaning that i would like to host a template that i would define that would trigger a DOI Mail with link all the details needed.

   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. 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

8. 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

   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. 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

10. 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

11. 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

12. 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

13. 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

14. 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

15. 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

    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

16. Set Preview Text via API

    I would like the ability to set preview text via API

    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. why i can't get webhook?

    when i invoker your api send email, when i receive email i should get a webhook ,but i can't get anything,why? my webhook is ok and test is receive .

    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

18. Properly handle headers encoding when the target MTA lacks SMTPUTF8 and the client app uses UTF8 when sending to mailjet

    When enabling UTF8 support between the client app and mailjet SMTP API, the client library generally encodes SMTP headers like the Subject using UTF8 rather than quoted-printable + US-ASCII. So when using any UTF8-ready SMTP client library (in our case the SmtpClient from .NET 6), a Subject like "Caractères accentués" will be sent to mailjet as "Subject: Caractères accentués" when UTF8 is enabled (SmtpDeliveryFormat.International in .NET), and "Subject: =?UTF-8?Q?=Caract=C3=A8res_accentu=C3=A9s?=" when it is not (SmtpDeliveryFormat.SevenBit in .NET).

    This is correct behavior from the client library, but there is an issue with mailjet when the recipient MTA does not support SMTPUTF8 itself: mailjet just forwards the headers as it received them in the first place, including the Subject encoding (i.e. mailjet sends a UTF8 Subject header value to a MTA that does not support UTF8). This results in broken subject messages in the recipient's mailbox (non-ASCII characters are replaced with "???", so in this example the recipient sees "Caract???res accentu???s"). This happens with the few email providers that do not support SMTPUTF8 (iCloud, yopmail, or any MTA using Postfix < 3.0).

    One odd thing to note is that mailjet DOES reencode the Subject header using quoted-printable + US-ASCII when it contains the "[" character, meaning "[test] Caractères accentués" will be correctly displayed in thoses mailboxes whereas "Caractères accentués" will not. The correct behavior would be to reencode the Subject header if the recipient does not list SMTPUTF8 as a supported extension, instead of reencoding it using the current logic.

    Possible workarounds:
    - ignore the issue - most mailboxes support SMTPUTF8 (iCloud and some self-managed mailboxes being notable exceptions) ;
    - always include the character "[" in your email subjects (e.g. use "[xxx]" prefixes) ;
    - disable UTF8 encoding in the client app (use SmtpDeliveryFormat.SevenBit in .NET) - however this means UTF8 email addresses will not be supported ;
    - keep UTF8, but force the Subject header to be encoded using quoted-printable + US-ASCII - this might not be possible depending on the level of control your SMTP library offers (e.g. this is not possible using the SmtpClient from .NET).

    When enabling UTF8 support between the client app and mailjet SMTP API, the client library generally encodes SMTP headers like the Subject using UTF8 rather than quoted-printable + US-ASCII. So when using any UTF8-ready SMTP client library (in our case the SmtpClient from .NET 6), a Subject like "Caractères accentués" will be sent to mailjet as "Subject: Caractères accentués" when UTF8 is enabled (SmtpDeliveryFormat.International in .NET), and "Subject: =?UTF-8?Q?=Caract=C3=A8res_accentu=C3=A9s?=" when it is not (SmtpDeliveryFormat.SevenBit in .NET).

    This is correct behavior from the client library, but there is an issue with mailjet when the recipient MTA does not support SMTPUTF8 itself:… 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

19. Rust SDK

    Pourriez-vous proposer un SDK pour Rust s'il vous plaît afin d'apporter un support complet aux devs de cette technologie

    merci

    Could you please propose an SDK for Rust in order to bring a complete support to the devs of this technology

    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

20. Pouvoir modifier le lien de tracking depuis l'API - Be able to modify the tracking link from the API

    Il serait bien de pouvoir modifier le lien de tracking personnalisé depuis l'API afin de pouvoir procéder à un paramétrage complet de la plateforme depuis un accès via cette API

    It would be nice to be able to modify the custom tracking link from the API in order to be able to proceed to a complete parameterization of the platform from an access via this API

    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