" api Archives - LuxSci

Posts Tagged ‘api’

Using Secure Email APIs to Improve Operational Efficiency

Tuesday, May 10th, 2022

APIs are just one tool that organizations can use to streamline operations and automate processes. This article explains how secure email APIs can save time in healthcare communications.

secure email api

What is an API?

API is an acronym that stands for “Application Programming Interface.” APIs enable companies to open up their applications’ data and functionality to external third-party developers, business partners, and internal departments. They allow services and products to communicate and leverage each other’s data and functionality through a documented interface. APIs simplify app development by allowing applications to work together.

APIs help business and IT teams collaborate. One example is the Weather Underground API. If a smartwatch developer wanted to display the weather on the watch face, they could use the Weather Underground API to source current weather data and local forecasts. Application developers do not have to create an entirely new weather database and keep it updated. Instead, the API enables them to use the Weather Underground’s meteorological data in their application.

APIs enable information to flow both ways. The smartwatch can display Weather Underground forecasts, and the API can report data back to the Weather Underground. This functionality enables interoperability and data sharing.

Email APIs

An email API gives applications the ability to send emails and retrieve analytics. Email APIs are often used to send transactional emails from applications like CRMs, EHRs, and other databases. Trigger-based emails are ideal for sending with an email API. In this situation, emails are sent when pre-determined conditions are met. For example, an order confirmation is a transactional, trigger-based email. A person buys a product online, the transaction is processed, and an email is sent to the buyer with their transaction details. The email is sent automatically with an email API.

Benefits of Secure Email APIs

Imagine if it was an employee’s responsibility to create and send every order confirmation email. It would be completely overwhelming. Besides saving time, some of the main benefits of email APIs include:

      • Easy to use and implement
      • Cost savings
      • Email deliverability improvements
      • Email list management
      • Reporting and analytics functionality
      • Personalization and customization
      • Enterprise-grade security

How to Use Secure Email APIs to Improve Operational Efficiency

Healthcare organizations are under increasing pressure to improve the patient experience. Online shoppers expect to see those order confirmation emails within a few minutes of finalizing their orders. Healthcare consumers using online communication tools expect the same experience from their healthcare providers. By expediting and personalizing patient communications, APIs can help increase patient satisfaction.

Thanks to the introduction of electronic health records, healthcare organizations have access to more patient data than ever before. Developers can use secure email APIs to send timely, trigger-based emails from EHR platforms.

Some examples of the types of emails that healthcare providers can send using an email API include:

  • Welcome emails
  • Appointment reminders
  • Patient satisfaction surveys
  • Flu shot and vaccine reminders
  • Password resets and other transactional emails

It works like this: the developer creates the email templates in advance and the criteria for email sending. The email is automatically sent when the conditions are met. For example, a developer may trigger a welcome email to send when:

1) a new patient is added to the database and

2) their first appointment date is set.

Email APIs can also pull information from the patient record to personalize the email. The welcome email may include the patient’s name and the date of their first appointment.

Other than updating the patient record, office administrators do not need to take additional actions to send the email. The email API automatically sends customized emails when appropriate.

Security and Privacy Considerations

Of course, developers working with patient data should not ignore HIPAA. It is essential to choose a vendor that understands the requirements. Failing to follow proper protocols can put patient data at risk and lead to data breaches.

For developers looking to create their own HIPAA-compliant APIs, the Office of the National Coordinator for Health Information Technology has put together a helpful guide. LuxSci also has API developer documentation to help integrate applications with our secure email API.

Conclusion

Email APIs are an essential part of digital health transformation and interoperability. Healthcare organizations should explore how APIs can improve their workflows and improve efficiency. LuxSci provides HIPAA-compliant and secure email APIs with Secure High Volume Email Sending. Contact us today to learn more.

Updated API Documentation and New Software Development Kits

Thursday, November 4th, 2021

LuxSci is pleased to announce new updates to our API documentation along with the release of new Software Development Kits (SDKs) for the following programming languages: C#, Python, JAVA, Ruby, and Node.js.

New Software Development Kits

Our new SDKs can be accessed from the links below:

C#

Python

JAVA

Node.js

Ruby

What is an API?

LuxSci’s application programming interface (API) allows account administrators to automate workflows and integrate LuxSci with other applications by writing their own programs or scripts. LuxSci’s API is REST-based and uses JSON for data transport. Our documentation also includes example client-side code that can be used to call LuxSci API endpoints. These simple examples can be used as a basis for building your own API client programs.

Do I have Access to LuxSci’s API?

LuxSci customers are able to access our API upon request. If you are an existing customer, simply ask our support staff to enable your account for access.

 

API Enhancements for DKIM Automation

Wednesday, December 2nd, 2020

DKIM, Domain Keys identified Mail, is a critical component to ensuring good INBOX delivery of email messages for day-to-day email, email marketing, and transactional email.  DKIM digitally signs outbound email so that the message recipients can verify that the messages originated from email servers authorized to send email from the sender.  I.e., it helps recipients identify and discard forged and fraudulent email messages while keeping legitimate ones.

API Enhancements for DKIM

In order to use DKIM with LuxSci, customers need to:

  1. Have LuxSci generate keys for each sending domain
  2. Update the DNS settings for each domain to publish the DKIM public key.

See LuxSci’s Help for our general DKIM setup instructions for more details.  These steps are pretty quick and easy, unless you have a large number of domains that you are sending email from.

To help such customers automate their workflow and manage their domains, LuxSci’s API has been augmented to enable management of DKIM keys for LuxSci customers.  The API now permits:

  1. Creation of new DKIM keys for new domains.
  2. Downloading the DKIM information needed for the DNS configuration.
  3. Deletion of DKIM keys for domains no longer in use.

Together with LuxSci’s other API endpoints, LuxSci customers can automate the addition and deletion of domains, email aliases, users, and now DKIM settings.  LuxSci is committed to continually expanding its API capabilities to enable and support automated workflows and processes.

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.

Read the rest of this post »