Erik's ToolBox Documentation
Index

Moosend Connector

The Moosend connector sends transactional email from Business Central through the Moosend (Sitecore Send) transactional API. Authentication is a single API key — the simplest of the three connectors to set up.

How It Works

You obtain an API key from your Moosend / Sitecore Send account, verify the sender address (and, ideally, the sending domain), and give Business Central the key plus the sender identity. Business Central then posts messages to the Moosend transactional endpoint.

Prerequisites

  • A Moosend (Sitecore Send) account whose plan includes transactional email. If the account

only has campaign features, the transactional send endpoint is rejected.

  • A verified sender address in Moosend (and, for good deliverability, a verified domain with

SPF and DKIM).

  • The Allow HttpClient Requests setting enabled for the ToolBox extension.

Step 1 — Get Your API Key

  1. Log in to your Moosend / Sitecore Send account and open Settings → API key.
  2. Copy the key. It authenticates every call, so treat it like a password.

Note: transactional email sending must be included in your Moosend plan. An account with only campaign features cannot use the transactional send endpoint.

Step 2 — Verify the Sender

  1. The address you send from must be a verified sender in Moosend. Add and confirm it under

the sender settings.

  1. For reliable inbox delivery, also verify the sending domain (SPF and DKIM records) —

unauthenticated senders often land in spam.

Step 3 — Register the Account in Business Central

  1. Search for Email Accounts → Add an email account → choose Moosend (ToolBox).
  2. Fill in the account card:
Field Description
Account Name A name to identify this account in Business Central.
Sender Email Address The verified sender address to send from.
Sender Name Optional display name shown as the sender.
API Base URL Leave at https://api.moosend.com/v3 unless your account runs on a different Sitecore Send host.
API Key The key from Step 1 (stored in IsolatedStorage, never in the database).
Enabled The send mode — see the Enabled modes.
Redirect Email Address Only used when Enabled (Redirect) is selected.

Step 4 — Verify the Setup

  • Test Connection validates the API key with a cheap read call.
  • Send Test Email sends a message from the sender address to itself through the transactional

endpoint — the definitive end-to-end proof.

Troubleshooting

Symptom Cause Fix
Test Connection fails with 401 or an invalid-key error Wrong or revoked API key. Copy the key again from the Moosend settings and re-enter it on the card.
Error mentions recipients excluded (e.g. "1 accepted, 1 excluded") Moosend rejected individual recipients: unsubscribed, on the suppression list, or an invalid address. The error lists each excluded recipient with the reason. Check the recipient in the Moosend suppression settings, or correct the address.
Sender-related rejection The sender address or domain is not verified. Complete Step 2.
Error about the payload or content size The API accepts at most 20 MB per call (body + base64-encoded attachments) and 1 MB of body content. The connector checks the 20 MB limit before calling. Reduce attachment sizes or send fewer attachments per message.

Good to know: the Moosend API can answer HTTP 200 and still report an error in the reply envelope (Code ≠ 0). The connector detects this and surfaces the real error message, so trust the error text in the outbox.

Test environments: use the Enabled setting on the account card — Enabled (No Sending) swallows all mail, Enabled (Redirect) reroutes everything to a single address. No need to touch the API key.