New API method to retrieve SMTP log for transactional email

We've launched a new API method to retrieve the SMTP log for a transactional email message. The method, Reports_GetSMTPLog_Transactional, is described in detail below.



The method takes, as input parameters, the account username, password, and the numeric Transactional ID corresponding to the transactional email for which the SMTP Log should be retrieved. The method was designed around the Transactional ID rather than a recipient email address, since the Transactional ID will always be unique per individual transactional email message. With email addresses, there can be multiple transactional emails to the same address within an account.

Thet Transactional ID can be retrieved from the User Interface in Reporting, or via other API methods, like Reports_Transactional_GetRecipients_XML.

The output of Reports_GetSMTPLog_Transactional includes the SMTP log as an XML string:




Note: This new method is in addition to our existing method that retrieves SMTP logs for broadcast email messages:



JangoMail is the only email service that offers access to SMTP logs for both broadcast email campaigns and transactional email, and is now also the only service to do so through an API. The full API, including documentation and test forms, is at http://api.jangomail.com/

Reports_GetSMTPLog
Returns the SMTP log session for the specified broadcast campaign's email address

Reports_GetSMTPLog_Transactional
Returns the SMTP log session for the specified transactional email message