> ## Documentation Index
> Fetch the complete documentation index at: https://docs-stage.bglobale.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sending Bulk Emails

> Send CS (bulk) emails to multiple addressees in a single API call by providing order IDs, an email type, and optional placeholders.

## Sending Bulk Emails (Merchant to Global-e)

Emails can now be sent to multiple addresses by issuing an API call providing order IDs and the email message type. Additionally, placeholders can be added to the mail message to dynamically add details to the email message content without code changes.

This API provides the following:

* Allow the merchant to send CS emails (Bulk Emails) on a single API by providing a list of order IDs
* Allow the merchant to specify the email address for sending the processing report
* Allow merchant the option to specify the return address, default as configured for CS/FinOps
* Monitor and log merchant actions
* Store the action results report for performance and success level measurements.
* Customize the email message template for full merchant customizations and look & feel

## Prerequisites

The following is to be prepared Before issuing the API:

* Select the **email type** and verify its template, from the existing types, or ask your CSM to create a template.
* Specify the **placeholders'** name and value, if you plan to add them to the email message.
* List the **Order ID**s that are the addressees of this mail.

<Note>
  A text resource value refers to predefined placeholders and their related values. The placeholders and their values are defined in the Admin platform, with the prefix `TR_`. A value can be a Global-e default value or merchant-specific value. Refer to your CSM for all predefined `TR_` placeholders, and for defining merchant-specific values.
</Note>

<div className="api-ref-card">
  <Card title="Send Bulk Emails — full request & response" icon="code" href="/api-reference/send-bulk-emails">
    Parameters, schema, examples, error codes for `POST /emails`.
  </Card>
</div>

## Use Cases

### Mail Message

In the following example, the Order ID is integrated into the email template, by adding the `orderId` placeholder.

<img src="https://mintcdn.com/globale-enterprise/tw35F3WiyJ8sxtxX/images/emails/mail-message-example.png?fit=max&auto=format&n=tw35F3WiyJ8sxtxX&q=85&s=7d98bfa686ff1e4388abab7a4cb4ea24" alt="Mail message example" width="1129" height="951" data-path="images/emails/mail-message-example.png" />

**Note**: When sending a list of Order IDs in the API request, each mail message will have the relevant ID for the mail recipient.

### Results Report Email

The following report is received detailing the result of the bulk emails API, sent to inform of a delayed fulfillment of a single order ID.

<img src="https://mintcdn.com/globale-enterprise/tw35F3WiyJ8sxtxX/images/emails/results-report-example.png?fit=max&auto=format&n=tw35F3WiyJ8sxtxX&q=85&s=ab4e5f4563a6ccaf94ddcc5324b1e288" alt="Results report email example" width="1546" height="470" data-path="images/emails/results-report-example.png" />

### Example

Request:

```json theme={null}
{
  "emailTypeName": "Delayedfulfillment",
  "senderEmailAddress": "globale@global-e.com",
  "reportToEmailAddress": "zivido@gmail.com",
  "orderIds": [
    "GE399999999GB"
  ],
  "placeholders": {
    "{DelayReason}": "TR_OverloadDelayReason",
    "{DelayDaysCount}": "2"
  }
}
```

Response:

```json theme={null}
"Processing is in progress. You will get an email after the process is complete."
```