Released Versions and Changes

Version numbers correspond to the overall LuxSci software release cycle, not just the API SDKs. This change list concerns changes to the SDKs only; changes to the back end that do not require downloading new versions of the SDKs are not included.

Version & Release Date Changes



    Added support for List and Template groups in the List and Template API endpoints.
  • New API endpoints for: adding, updating, and deleting Secure Marketing List Groups
  • New API endpoints for: adding, updating, and deleting Template Groups



  • New API endpoints for: adding, updating, and deleting Campaigns.



  • New API endpoints for: listing and creating Custom Fields
  • New API endpoints for: listing and managing files and directories in the Content Library
  • New API endpoints for: listing Secure Marketing v3 Campaigns
  • The Email Delivery Status "Count" API Reports now support a parameter for measuring the number of messages that have been queued more than a sepcific amount of time.



  • LuxSci now tracks the Enhanced SMTP Codes returned by email servers as part of the email delivery process and exposes these through the email delivery report API calls.



  • The Secure Marketing v3 deleteList endpoint now supports a "contacts_only" parameter which enables deleting all contacts in a list without deleting the list itself.



  • The getEmailTemplateList API call has been updated to allow selection of only those Templates owned by a specific user. I.e., for cases when a user belongs to a Team and, otherwise, all Team Templates would be returned.



  • New API calls for managing Contacts and Contact Lists for Secure Marketing v3 customers.
  • New API calls for retrieving summary report data of email delivery and engagement data that are particularly useful for creating automated email and WebHook alerts.
  • New API calls for retrieving detail and summary reports about what users are in your account, with optional restrictions based on the date the users were created.



  • The server status API call now returns email sending warm-up rate limiting status information
  • New setServerSendngRate API call to set email sending rate limits and to suspend/unsuspend email processing
  • New serverEmptyEmailQueues and serverEmptyAllEmailQueues commnds to remove messages from email queues.



  • The Email Sending API endpoint now support the optional "template_format" parameter. When using templates that have both text and html content, "template_format" allows you to select only one of these to include in the message, rather than both.



  • Secure Marketing: Added an API call for adding many contacts at once.
  • Secure Marketing: Added an API calls for List Groups and Campaign Groups



  • Email templates support Content Tags. These are HTML and/or text blocks that can be centrally managed and included in templates.
  • API calls for managing Content Tags have been added.



  • Email templates support shared access.
  • Email template functions now support the is_private field.
  • Email reports now include the template_id of the template used in sending, as appropriate. Thay also support filtering by template_id.



  • The email template functions now return the date and time that each template was last used.
  • Email templates now support "preheader" text.



  • The user- and account-level email delivery status reports now (a) include if each message was involved in an "unsubscribe" action by the message recipient, and (b) allow filtering to select only those messages that were involved in an "unsubscribe" action by the message recipient.
  • New API endpoints getAccountSuppressionReport and getUserSuppressionReport have been added. These provide a full report-style interface to accessing email suppressions (unsubscribes) and also include additional information (beyond that returned by the simpler functions getUserSuppressionList and getAccountSuppressionList) about each suppression—the sendmail_id of the message that triggered the unsubscribe event and expires which indicates when, if ever, the suppression will be automatically removed from the system.



  • The API endpoint for High Volume SMTP emailing (sendEmail) now supports a per-message "priority" setting. This allows customers concurrently sending large numbers of messages with varying priority to have higher priority messages be processed and delivered before lower priority ones — even if the lower priority ones are already queued for processing and delivery.



  • All API reporting requests now support an "asynchronous" mode that allows large reports (containing millions of rows) to be generated in the background. Once complete, the resulting CSV report is uploaded to a customer-specified SFTP server.
  • The API now includes endpoints to check on the progress on asynchronous report generation "jobs".



  • The API endpoint for High Volume SMTP emailing (sendEmail) now supports adding a "method" parameter to email message attachment Content-Type headers. This addition supports the sending of calendar (i.e., iCal) attachments in email messages, where the "method" parameter guides how these attachments are interpreted by email and calendar viewers.



  • The API endpoint for High Volume SMTP emailing (sendEmail) now supports the "sandbox" parameter, which is very useful for integration and performance testing without actually sending email messages to your recipients or using up your sending quota.



  • The API endpoint for High Volume SMTP emailing (sendEmail) has been optimized. It now accepts email messages up to 20x faster.



  • If your API session has timed out, the SDK will detect this and automatically re-authenticate your API session so that you do not have to manage re-authentication in your API client program for calls that happen after an IDLE time of more than 15 minutes.
  • The SDKs now support changing the active API configuration by permitting use of the authentication call with a different authentication credentials after the first authentication has happened. In this way, the API client can switch between API configurations as needed simply by authenticating to the new configuration.



  • Corrected support for custom contact fields in Secure Marketing API calls.



  • SDKs updated to automatically update the session state token after each API call so that an authorization call only needs to be made after 15 minutes of IDLE time, not after 15 minutes from starting to use the API.





  • Initial versions of SDKs released.