For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Help CenterAPI KeysStatusSign In
GuidesAPI ReferenceChangelog
GuidesAPI ReferenceChangelog
  • Getting started
    • Overview
    • Quickstart
    • Authentication
    • Rate limits
  • Messaging API
    • Send transactional email
    • Send transactional SMS
    • Send transactional WhatsApp
  • Marketing Platform
    • Manage your contacts
    • Track website activity
    • Send WhatsApp campaigns
    • Weekly event exports
  • Webhooks
    • Getting started
    • Conversations webhooks
    • Payment webhooks
    • Marketing webhooks
    • Transactional webhooks
    • Loyalty webhooks
    • Batched webhooks
    • Secure webhook calls
    • Meetings and phone webhooks
    • Push notification webhooks
    • Sales CRM webhooks
  • Conversations
    • Getting started
    • Customize the chat widget
    • JavaScript API reference
    • REST API reference
    • Conversations webhooks
  • eCommerce
    • Activate eCommerce app
    • Manage product categories
    • Manage products
    • Manage orders
    • Coupon collections
    • eCommerce tracker events
  • Loyalty
    • Overview
    • Set up a program
    • Enroll members
    • Credit & debit points
    • Read member data
    • Best practices
  • Custom Objects
    • Custom objects management
  • Brevo tracker and events
    • Getting started
    • JavaScript implementation
    • REST implementation
    • Legacy tracker documentation
    • Events
  • Accounts and settings
    • Senders and domains
      • Sender creation and management
      • Domain creation and management
      • Domain authentication and validation
    • User activity logs
    • External feeds
    • Invited users
LogoLogo
Help CenterAPI KeysStatusSign In
On this page
  • 1. Create a new sender
  • 2. Update a sender
  • 3. Get the list of all your senders
  • Delete a sender
Accounts and settingsSenders and domains

Sender creation and management

Was this page helpful?
Previous

Domain creation and management

Next
Built with

See the public API reference for senders at API Reference > Senders. The endpoints are covered one by one, starting with Create a new sender.

1. Create a new sender

Send a POST request to https://api.brevo.com/v3/senders. Sample cURL request:

1curl --request POST \
2 --url https://api.brevo.com/v3/senders \
3 --header 'accept: application/json' \
4 --header 'api-key: ' \
5 --header 'content-type: application/json' \
6 --data '
7{
8 "ips": [
9 {
10 "ip": "123.98.689.7",
11 "domain": "mycompany.com",
12 "weight": 50
13 }
14 ],

Endpoint parameters:

AttributeDatatypeDescriptionValue
nameStringFrom Name to use for the senderNewsletter
emailStringFrom email to use for the sender. A verification email will be sent to this address.newsletterr@mycompany.com
ipsArray of objectsMandatory in case of dedicated IP. IPs to associate to the senderIP objects

Since ips is an array of objects, it has sub-attributes:

AttributeDatatypeDescriptionValue
ipStringDedicated IP available in your account123.98.689.7
domainStringDomain of the IPmycompany.com
weightInt64Weight to apply to the IP. Sum of all IP weights must be 100. Should be passed for either ALL or NONE of the IPs. If it’s not passed, the sending will be equally balanced on all IPs.50

Using ips as array of objects

You can associate multiple dedicated IPs with a single sender.


Response

Response codeMessageDescription
201Sender createdSender was created.
400Bad requestParameters are in the wrong format.

2. Update a sender

Send a PUT request to https://api.brevo.com/v3/senders/{senderId} to update an existing sender. Sample cURL request:

1curl --request PUT \
2 --url https://api.brevo.com/v3/senders/24 \
3 --header 'accept: application/json' \
4 --header 'api-key: ' \
5 --header 'content-type: application/json' \
6 --data '
7{
8 "ips": [
9 {
10 "ip": "123.98.689.7",
11 "domain": "mycompany.com",
12 "weight": 50
13 }
14 ],
15 "name": "Newsletter",
16 "email": "newsletter@mycompany.com"
17}
18'

The Update a sender attributes split into path params and body params.


Path params

AttributeDatatypeDescriptionValue
senderIdInt64Id of the sender24

Body params

AttributeDatatypeDescriptionValue
nameStringFrom Name to use for the senderNewsletter
emailStringFrom email to use for the sender. A verification email will be sent to this address.newsletterr@mycompany.com
ipsArray of objectsMandatory in case of dedicated IP. IPs to associate to the senderIP objects

Since ips is an array of objects, it has sub-attributes:

ipStringDedicated IP available in your account123.98.689.7
domainStringDomain of the IPmycompany.com
weightInt64Weight to apply to the IP. Sum of all IP weights must be 100. Should be passed for either ALL or NONE of the IPs. If it’s not passed, the sending will be equally balanced on all IPs.50

Response

Response codeDescriptionMessage
204Sender was updated.Sender updated
400Missing or invalid parameter.Bad request
404Sender ID is missing or incorrect.Sender ID not found

3. Get the list of all your senders

Send a GET request to https://api.brevo.com/v3/senders. Sample cURL request:

1curl --request GET \
2 --url 'https://api.brevo.com/v3/senders?ip=192.168.8.138&domain=mydomain.com' \
3 --header 'accept: application/json' \
4 --header 'api-key: '

Endpoint attributes:

AttributeDatatypeDescriptionValue
ipStringFilter your senders for a specific ip192.168.8.138
domainStringFilter your senders for a specific domainmydomain.com

Response

Response codeMessageDescription
200List of sendersReturns the list of senders.
400Bad requestReturned for invalid or wrong parameters.

Delete a sender

Send a DELETE request to https://api.brevo.com/v3/senders/{senderId}. To implement this endpoint in your preferred language, use the code below.

Sample cURL request:

1curl --request DELETE \
2 --url https://api.brevo.com/v3/senders/245 \
3 --header 'accept: application/json' \
4 --header 'api-key: '

The only attribute is senderId, returned in the response when you create a sender.

AttributeDatatypeDescriptionValue
senderIdInt64Id of the sender245

Response

Response codeMessageDescription
204Sender deletedSender was deleted.
400Bad requestInvalid or missing parameters, or other request issue.
404Sender Id not foundSender ID to be deleted was not found.