Skip to main content

Bloomreach Transactional Email API Client

A nonofficial, JavaScript, feature complete, client library for sending transactional emails via Bloomreach.

The aim of the bloomreach-transactional-email package is to get you going with the Bloomreach Transactional Email API as quickly as possible. The sendEmail function takes the minimum number of required parameters to send an email. Other parameters are optional. Full details of all the options can be found in the Bloomreach Transactional Email API documentation.

bloomreach-transactional-email  uses axios, as a peer dependency, to make HTTP calls.

Install

npm i -save bloomreach-transactional-email

Basic Examples

If you have Customer IDs and a default email integration with a sender name and address setup in Bloomreach then you can use the minimum configuration to send an email by specifying a HTML body and a subject:

import { sendEmail } from 'bloomreach-transactional-email';

const auth = {
    username: '...',    // Your APIKeyID
    password: '...',    // Your APISecret
    baseUrl: 'https://api.exponea.com', // Your base url
    projectToken: '...', // Your project token
};

const campaignName = 'MyCampaign';

const customerIds = {
    registered: 'marian@exponea.com'
};

const htmlContent = {
    html: '<!DOCTYPEhtml><body>Hello world</body></html>',
    subject: 'SubjectExample',
}

await sendEmail(auth, campaignName, customerIds, htmlContent);


If you have a template set up you can also send an email using it:

const templateContent = {
    templateId: '60758e2d18883e1048b817a8',
    params: { first_name: 'Marian' }
}

await sendEmail(auth, campaignName, customerIds, templateContent);


If you don’t have Customer IDs setup in Bloomreach you can specify the email address to send the email to (you still need to specify Customer IDs). If you have language variants of your template, you can specify the language. You can also specify the sender name and sender address:

await sendEmail(
    auth,
    campaignName,
    customerIds,
    htmlContent,
    {       
            email: 'jon.doe@example.com',
            language: 'en',
            senderAddress: 'Marian',
            senderName: 'marian@exponea.com'
    }
);


Integrations

You can specify either a single integration:

await sendEmail(
    auth,
    campaignName,
    customerIds,
    htmlContent,
    {       
            integrationId: "5b337eceeb7cdb000d4e20f3"
    }
);


or up to two integrations, a primary and a backup in case the primary fails, with individual sender addresses:

await sendEmail(
    auth,
    campaignName,
    customerIds,
    htmlContent,
    {       
        integrations: [
            {
                id: "5b337eceeb7cdb000d4e20f3",
                senderAddress: "marian@exponea.com",
            },
            {
                id: "3f02e4d000bdc7beece733b5",
                senderAddress: "marian@exponea.com",
            }
            ]
    }
);


Transfer Identity

You can specify a transfer identity of:

  • enabled
  • disabled
  • first_click

await sendEmail(
    auth,
    campaignName,
    customerIds,
    htmlContent,
    {       
            transferIdentity: 'disabled'
    });


Attachments

You can add an array of attachments with base64 encoded content:

await sendEmail(
    auth,
    campaignName,
    customerIds,
    htmlContent,
    {}, // Options object can also be undefined
    [
        {
            filename: 'example1.txt',
            content: 'RXhhbXBsZSBhdHRhY2htZW50',
            contentType: 'text/plain',
        },
        {
            filename: 'example2.txt',
            content: 'RXhhbXBsZSBhdHRhY2htZW50',
            contentType: 'text/plain',
        },
    ]);


Settings

You can also add:

  • Custom Event Properties
  • Custom Headers
  • Url Params
  • Transfer User Identity
  • Consent Category
  • Consent Category Tracking


Check the Bloomreach Transactional Email API documentation for details:

await sendEmail(
    auth,
    campaignName,
    customerIds,
    htmlContent,
    {}, // Options object can also be undefined
    [], // Attachments array can also be undefined
    {
        customEventProperties: {
            bannana: 'yellow',
            1: 2,
        },
            customHeaders: {
            source: 'your-company',
            1: 2,
        },
        urlParams: {
            source: 'email',
            1: 2,
        },
        transferUserIdentity: 'first_click',
        consentCategory: 'sms',
        consentCategoryTracking: 'sms',
    });


Comments

Popular posts from this blog

It's great to be back at the ACCU Conference 2025!

Last week I was back at the ACCU Conference in Bristol, for the first time since I gave an opening keynote in 2019 . In March 2020, COVID hit the UK and I got out of the habit of attending and speaking at conferences. Plus the ACCU Conference, and the organisation in general, took a big step back towards C++ and that hasn’t been relevant to me for nearly two decades. It’s taken until now, 2025 for me to want to talk again, and I was really pleased to be accepted for the ACCU Conference again. It was just a 20 minute session and I only attended for the day I was speaking. There was enough varied content for it to be interesting to me and I’m hoping to be back for the full conference next year. I really enjoyed attending and it was great to catch up with people I hadn’t seen for years. I felt re-engaged and particularly liked being asked if I’d been to nor(DEV):con . Learning to stop writing code (and why you won't miss it) Daisy Hollman I should have read the summary of the openin...

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

I, Robot

The Foundation series has been my go to for a good, enjoyable read over the last two years, so naturally I moved on to Asimov’s Robot series afterwards. However, the short stories in I, Robot were mostly a disappointment. They feel self indulgent, with too much philosophy and science, Asimov showing off, and not enough story. The most enjoyable moments come from the stories featuring Gregory Powell and Mike Donovan. Their banter and the relationship between them provide some much needed amusement and were easily the highlight of the book for me. However, it did give me food for thought for the current potential issues with the rapid development of AI at the moment, and the many concerns around safety. I wonder if all we need is: An AI may not injure a human being or, through inaction, allow a human being to come to harm. An AI must obey the orders given it by human beings except where such orders would conflict with the First Law. An AI must protect its own existence as long as such p...