> For the complete documentation index, see [llms.txt](https://ledsak.gitbook.io/docs-for-ledsak/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ledsak.gitbook.io/docs-for-ledsak/integrations/brevo.md).

# Brevo

### Overview

Brevo (formerly Sendinblue) allows users to send bulk emails efficiently using its API. This document outlines the process of configuring and sending bulk emails using the provided sender name, sender email, and API key.

### Prerequisites

Before sending bulk emails, ensure you have the following:

* A Brevo account
* A valid API key
* Sender email and sender name configured in Brevo

### **Step 1: Configure API Credentials in Brevo**

#### Create and manage your API keys

In this article, we will explain what an API key is and how you can create a new one or delete an existing one.

💡 Good to knowOnly Brevo users with **API keys permission** can access the [SMTP & API page](https://account.sendinblue.com/advanced/api), create a new API key, or delete an existing API key. To learn more about user permissions and permission levels, check our dedicated article [User permissions and permission levels in Brevo](https://help.brevo.com/hc/en-us/articles/360001096239).

#### What is an API key? <a href="#h_01jjm98trb0df59m7e1r32tc08" id="h_01jjm98trb0df59m7e1r32tc08"></a>

An API key is a code used to identify and authenticate an application or user. It acts as a **unique identifier** and **provides a secret token** for authentication purposes.

For example, you can use an API key to **connect your website or information system to Brevo**. This will enable you to automatically and manually trigger certain actions between the two.

With an API key, you can also **connect to our API** to automatically add new contacts, as well as do more complex tasks, such as:

* Creating and scheduling campaigns from the API.
* Exporting users that belong to particular lists.
* Exporting campaign statistics, etc.

To access the full list of commands that you can use with our API, check [our API documentation](https://developers.brevo.com/reference/email-campaigns-1).

#### Where can I find my API keys? <a href="#h_01jjm98trbab6qyf9c07mz5gxw" id="h_01jjm98trbab6qyf9c07mz5gxw"></a>

To protect your API keys and make them more secure, your existing API keys are **not visible** from your Brevo account. Only the last digits of the keys are displayed on the [SMTP & API page](https://app.brevo.com/settings/keys/api) so that you can distinguish between several keys if necessary:

![API\_keys.jpg](https://help.brevo.com/hc/article_attachments/21011330345490)

That's why we strongly suggest you store your API key in a safe environment when you create your API key. If you've lost your API key, we recommend you create a new one, store it in a safe environment, and replace the previous one.

#### Create an API key <a href="#h_01gw6zqekz072sfgk03n9r6ve6" id="h_01gw6zqekz072sfgk03n9r6ve6"></a>

💡 Good to knowThe account owner will receive an email notification, including details such as the IP address and location, whenever an API key is created or deleted from the account.

When configuring an integration with your Brevo account, you may need to create a new API key:

1. Go to [**Your account name** > **SMTP &** **API**](https://account.sendinblue.com/advanced/api).
2. Click **Generate a new API key**.\
   ![create\_new\_key.jpg](https://help.brevo.com/hc/article_attachments/21011360201490)
3. Name your API key. Make sure it specifies with which integration the API key will be used so that you can easily recognize it.
4. Click **Generate**.\
   ![name\_key.jpg](https://help.brevo.com/hc/article_attachments/21011330365458)
5. Copy your API key and store it in a safe environment.\
   ❗️ ImportantYour API key is **only visible during this step**. Once your API key is created, you won't be able to copy it anymore and you'll need to create a new one if you lose it.
6. Click **OK**.\
   ![copy\_key.jpg](https://help.brevo.com/hc/article_attachments/21011330362642)

You have now successfully created a new API key.

#### **Step 2: Connect Brevo with Ledsak**

1. Log in to your **Ledsak** account.
2. Go to the **Integrations** section.
3. Select **Brevo** from the list of available integrations.
4. Click on **Connect** and enter the **API key** you generated earlier.
5. Follow any additional prompts to complete the authentication.

Brevo account to connect:&#x20;

<figure><img src="/files/4Mh5OKjPDwtHJkSBQI9Y" alt=""><figcaption><p>Click to Connect Brevo</p></figcaption></figure>

#### Fill the Field:

<figure><img src="/files/yKMoUvknPUJQov1wNoKt" alt=""><figcaption><p>Fill The API key </p></figcaption></figure>

#### Connected Account:&#x20;

<figure><img src="/files/C4sEPxjaa6qImisPfQBg" alt=""><figcaption><p>Check the helath of the account.</p></figcaption></figure>

#### View History

<figure><img src="/files/DMyy4jFMbusEhqGDKx09" alt=""><figcaption><p>See the Sent History.</p></figcaption></figure>

#### Send Bulk Email for multiple lead:

* Go to All Leads
* Select the Multiple Lead
* Click on Bulk Action
* Click on Bulk Email&#x20;
* Select Template and Sent


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ledsak.gitbook.io/docs-for-ledsak/integrations/brevo.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
