Skip to main content
POST
Send Consumer Profile manual e-letter

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

consumer
integer
required

Consumer account ID.

Body

application/json
content
string
required

HTML, Markdown, or plain-text e-letter body. Content must contain visible text after Markdown and HTML are rendered and stripped. Embedded base64 editor images are stored on the s3 disk and replaced with S3 object URLs.

Example:

"<p>Hello, please review your secure e-letter.</p>"

Response

E-letter delivered and communication history recorded.

message
string
required
Example:

"Secure eLetters delivered."

data
object
required
Last modified on July 20, 2026