kurrier
Kurrier APIRoutes

Email

Send email through the Kurrier hosted API.

Send email

Use the Email API to send a message from an identity available to the authenticated Kurrier user.

For authentication and the hosted API base URL, see API Authentication.

Send a message

POST /email/send

curl 'https://YOUR_KURRIER_HOST/api/kurrier/email/send' \
  -X POST \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "identityId": "1a9b317a-8a84-493a-b9f8-83a3800861e2",
    "to": "ada@example.com",
    "subject": "Welcome to Kurrier!",
    "html": "<p>Hello!</p>",
    "text": "Hello!"
  }'
FieldDescriptionExample
identityId (required)ID of the Kurrier identity to send from. The API key must have access to this identity."1a9b317a-8a84-493a-b9f8-83a3800861e2"
to (required)Recipient email address."ada@example.com"
subject (required)Subject line of the email."Welcome to Kurrier!"
html (required unless text is provided)HTML version of the message body."<p>Hello!</p>"
text (required unless html is provided)Plain-text version of the message body."Hello!"
ccComma-separated CC recipients."manager@example.com,ops@example.com"
bccComma-separated BCC recipients."audit@example.com"
attachmentsAttachments encoded as objects containing filename, contentType, and Base64 content.[{ "filename": "photo.jpg", "contentType": "image/jpeg", "content": "BASE64_DATA" }]

The selected identity determines which configured provider or SMTP account sends the message.

Response

On success, Kurrier returns a unique message ID:

{
  "messageId": "3c152a84-6559-4094-a1da-3f1a3209866d"
}

Store the message ID with your application record when you need to correlate the send request with later processing or webhook events.

Before sending from production

  • Keep the API key in trusted server-side code.
  • Confirm that the authenticated user can access the selected identity.
  • Provide both HTML and plain-text bodies when possible.
  • Base64-encode attachment content and avoid sending files larger than your workspace or provider permits.
  • Do not retry an ambiguous request automatically unless your application can prevent duplicate messages.

On this page