Secure Messaging APIs provide a way for your systems to integrate with and take advantage of secure messaging features that meet HIPAA privacy standards.
By tying into these API endpoints, your system will be able to immediately leverage secure messaging without the need to manage user security, message archiving, sending and receiving messages (of course!), eventing, etc.
As required by HIPAA compliancy standards, all messages are encrypted in transit via secure TLS, and then message bodies at rest are stored using secure 256-bit AES encryption.
First you'll need an organization and API key. Please request to receive one.
Once your organization account is ready, you'll be able to setup sub-organization accounts under yours, read messages that were sent from your organization, manage users, send messages, etc.