Query the LuxSci API for Email Sending and Delivery Status Reports
LuxSci’s API has been expanded to enable automated queries for reports of:
- What messages have been sent from SMTP and/or WebMail
- The current delivery status (tracking) of these messages
- Feedback loop notices for these messages
- The history of SMTP login failures and sending failures due to sender usage problems
All of these reports are available at the account level (e.g. to download information for one or all users in an account) and at the user level (where someone using the user API can query data about his/her own sending activity). Each API request can return up to 50,000 matches or 50MB of data and you can easily submit multiple queries to “page” though very large result sets. The queries support refinement by date range, customization of the number of matches returned at once, and include report-specific search capabilities so that, for example, you could find only message sent to a particular person or which have a particular delivery status.
The new reports in more detail:
The details of all recently sent email messages for all account users or a specific user. This includes information such as the date/time sent, show sent it, the message size and tracking code, the subject, the complete recipient list, the sender from address, the IP of the sending computer, if the SecureLine was used, etc.
This is similar to the “messages sent” report, but contains a separate entry for every recipient of every message. In addition to tracking information similar to the messages sent report, you also receive the delivery status (e.g. failed, queued, successfully delivered) and the delivery details — I.e. exactly what the recipient server said when the message was accepted or, perhaps, why it is queued. The delivery status report also includes details on of TLS was used during transport (and what ciphers were used) and if SecureLine was used for encryption (and what encryption method was used).
Feed Back Loops
All ISPs allow their users to “mark messages as SPAM”. Some, can send an alert back to the sending ISP to inform them of that action and let them know what message was considered “spam”. This is a “feed back loop”. LuxSci has feedback loops with many large ISPs and we process these reports automatically for you. You can use the feed back loop report to discovery newly reported messages that were considered spam and use this information to prune people who do not want your messages from your mailing lists.
SMTP Login Failures and Sending Rejections
If you use the wrong password for SMTP, then your login will be rejected and your message will not be sent. Similarly, your message could be rejected for other customer-side reasons such as not using TLS encryption (if that is required), not using a proper SMTP port, exceeding your sending limits, etc. The Login/Sending Failure report allows you to see these rejections in real time so you can take action. E.g. if you have an automated system that is sending mission critical messages, you could use this API call to make sure that it is not failing to send. Even if your program is smart enough to detect a login failure or sending failure, it is always good to have a second, independent check for critical systems.
Administrators can also use this tool to alert them of users who may be having issues.
The delivery status, feed back loop, and sending failure reports are also available for automatic emailing to user or administrator email addresses on a periodic basis (e.g. from every 15 minutes if there is data or once/day). The API is great for automation; email is great for manual “eyes on”.
How do you get started?
Customers and those with Free Trials can find our API documentation in our member’s help:
To gain access to the API, you need to make a support ticket requesting that it be enabled for your account. There is no charge the use of our API.
Read: What can the LuxSci API Do?