" api Archives - LuxSci FYI Blog: Learn about HIPAA email encryption, secure email encryption, and more

Posts Tagged ‘api’

Email Templates for SMTP and API Secure Email Sending

Wednesday, March 18th, 2020

Server-side email templates that can be utilized when sending email messages through LuxSci’s APIs and LuxSci’s SMTP services are now available.  In particular, users can:

  1. Create and manage up to 100 templates per user through LuxSci’s web site or via API commands.
    1. Templates can not only define the subject and bodies of the messages that use them, they can also control how these messages will be encrypted (or not).
  2. Send messages using templates via API commands or SMTP — so message content can be retrieved from the server-side templates rather than sent with every message
  3. Use dynamic place holders so the template content can be customized on a per-message basis (i.e., like “mail merge”).
  4. Send unique per-message attachments that will be attached to the template-derived messages.

That’s it — templates made simple.

HaveIBeenPwned? Selecting passwords that are not known to Hackers

Friday, September 6th, 2019

Users tend to reuse passwords to make their life simple.  This includes reusing the same passwords across multiple sites and using the same passwords for years and years.

This is bad of course.  We see it in the news so frequently that no one is surprised that millions of accounts are compromised at companies every week.  What happens to this compromised data?  Very often it is dumped online where anyone can see it.  In fact, a vast collection of compromised information from usernames and passwords to addresses to employment histories and more is or has been available online related to all of these compromised web accounts.

haveibeenpwned

Read the rest of this post »

API Updates: Retrieve Dedicated Server Status on Demand

Monday, July 29th, 2019

LuxSci’s secure REST API enables LuxSci’s customers to automate account management activities, send secure email messages and secure texts, download custom reports, integrate their web sites with LuxSci WebMail using single sign on, and more.

As frequently happens, at LuxSci, we have added some more features to our API at the request of current customers.  These are two new API calls related to dedicated servers.  With these calls, you can take inventory of all of the dedicated servers that you gave with LuxSci (be that one or 20 or more) and then request the current status of each one.  Additionally, we have updated our API documentation guides.

API Updates

New Functions

The API has two new functions for accessing information about dedicated servers. In order to use these functions, you will need to ensure that the configuration that you are using has the “Dedicated Servers – Servers Report” access control permission enabled.   LuxSci’s API is designed with security in mind – existing configurations do not have permission to use significantly new/different features that are added over time until you explicitly grant such access.

Reports:  All Servers

The first new command returns a current list of add dedicated servers assigned to your account.  For each server this includes information such as the server name, unique Id, amount of RAM, number of CPU cores, etc.  This is all static information; information not directly related to the current health and uptime of your server.

Report: Server Status

For any particular server in your account, you can request the server status.  In addition to the static information about your server that you get from the all servers report, the server status report also includes the current values of:

  • If the server is up and responding.
  • How long since the server was last rebooted.
  • The 1-minute, 5-minute, and 15-minute server load averages (divided by the number of CPU cores the server has).
  • How much RAM and SWAP space is available and used.
  • How much network bandwidth has been used in the last 15 minutes, inbound and outbound.
  • Information about all mounted disks: How much space they have, how much is free, and what the current percentage I/O load is.
  • How many email messages are in your outbound email queues.

Accessing the Application Programming Interface

To start using the API, customers should first review the API documentation.  Then, proceed to the API section of your LuxSci account administration pages and create a configuration and assign what types of functions your API configuration should be permitted to perform.

If you have questions, please contact LuxSci support.

Automating the Sending of Secure Messages

Monday, February 1st, 2016

Do you have an application or system that needs to send secure messages on demand?  Do you need the flexibility to encrypt messages in different ways, to include files, HTML, and read receipts, or to have the messages be fully HIPAA compliant?

LuxSci has added secure messaging functionality to its Application Programming Interface (API).

Customers with SecureLine, LuxSci’s message encryption service, can now send secure messages though LuxSci’s REST API.  Features of this service include:

  1. Up to 100 recipients/message  (total daily and monthly recipient limits also exist and can be negotiated).
  2. Up to 70MB of content (body and attachments) per message.
  3. Email encryption via SMTP TLS, Escrow, PGP, and/or SMIME.
  4. The ability to toggle between use of TLS and Escrow on a per-message basis, depending on the level of security needed.  See: next generation opt-in email encryption.
  5. Message delivery tracking
  6. Read receipts — invisible to the recipient and reliable (with SecureLine Escrow).

If you would like to give LuxSci’s SecureLine messaging API a try, please contact LuxSci support and we can enable API access for your real or free trial account.

See also our General API Usage guide, and our API User Functions guide.

Query the LuxSci API for Email Sending and Delivery Status Reports

Thursday, July 16th, 2015

LuxSci’s API has been expanded to enable automated queries for reports of:

  1. What messages have been sent from SMTP and/or WebMail
  2. The current delivery status (tracking) of these messages
  3. Feedback loop notices for these messages
  4. 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.

These reports are available to all customers — business email, dedicated, and High Volume email sending.

Read the rest of this post »

LUXSCI