How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Brevo

brevo Senders API

Manage sender identities used for transactional email sending.

Documentation Provider Profile APIs.io OpenAPI GitHub

brevo Senders API is one of 53 APIs that Brevo publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Senders. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 7 operations across 5 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.brevo.com/v3.

7 operations 5 paths 29 schemas 1 DELETE3 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.brevo.com/v3
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

brevo Senders API declares 2 security schemes for authenticating requests. An API key is passed in the header as api-key (api-key). An API key is passed in the header as api-key (apiKeyAuth).

  • api-key — The API key should be passed in the request headers as api-key for authentication.
  • apiKeyAuth — Brevo API key passed in the api-key request header for authentication.

Paths & Operations 7

Across 5 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

senders 7
GET
/senders
Get email senders
getSenders 3 params → 200400
POST
/senders
Create email sender
createSender 1 param body → 201400
PUT
/senders/{senderId}
Update a sender
updateSender 2 params body → 204400404
DELETE
/senders/{senderId}
Delete a sender
deleteSender 2 params → 204400404
PUT
/senders/{senderId}/validate
Validate a sender using OTP
validateSenderByOTP 2 params body → 204400404
GET
/senders/ips
Get all the dedicated IPs for your account
getIps 1 param → 200400
GET
/senders/{senderId}/ips
Get all the dedicated IPs for a specific sender
getIpsFromSender 2 params → 200400404

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are SendersGetResponsesContentApplicationJsonSchemaSendersItems (5 properties), SendersIpsGetResponsesContentApplicationJsonSchemaIpsItems (4 properties), SendersSenderIdIpsGetResponsesContentApplicationJsonSchemaIpsItems (4 properties), Senders_createSender_Response_201 (3 properties). Each schema is shown below with its type and property counts.

CreateSenderRequestBadRequestError
object
2 properties 2 required
SendersPostRequestBodyContentApplicationJsonSchemaIpsItems
object
3 properties 2 required
SendersGetResponsesContentApplicationJsonSchemaSendersItemsIpsItems
object
3 properties 3 required
Senders_getIpsFromSender_Response_200
object
1 property 1 required
SendersSenderIdDeleteResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
SendersSenderIdIpsGetResponsesContentApplicationJsonSchemaIpsItems
object
4 properties 4 required
SendersSenderIdPutRequestBodyContentApplicationJsonSchemaIpsItems
object
3 properties 2 required
SendersSenderIdIpsGetResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
SendersGetResponsesContentApplicationJsonSchemaSendersItems
object
5 properties 5 required
GetIpsRequestBadRequestError
object
2 properties 2 required
DeleteSenderRequestBadRequestError
object
2 properties 2 required
Senders_getSenders_Response_200
object
1 property
SendersSenderIdValidatePutResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
GetIpsFromSenderRequestBadRequestError
object
2 properties 2 required
GetSendersRequestBadRequestError
object
2 properties 2 required
errorModel
object
2 properties 1 required
SendersIpsGetResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
ValidateSenderByOTPRequestBadRequestError
object
2 properties 2 required
SendersIpsGetResponsesContentApplicationJsonSchemaIpsItems
object
4 properties 4 required
UpdateSenderRequestBadRequestError
object
2 properties 2 required
SendersSenderIdPutResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
Senders_createSender_Response_201
object
3 properties 1 required
Senders_getIps_Response_200
object
1 property 1 required
SendersGetResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
SendersPostResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
CreateSenderResponse
object
1 property
SenderList
object
1 property
CreateSender
object
2 properties 2 required
ErrorResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

brevo-senders-api-openapi.yml Raw ↑

Other APIs Brevo publishes across the network.

brevo Agent Status API
AE Profile APIs.io
brevo Automated Messages API
AE Profile APIs.io
brevo Campaign Statistics API
AE Profile APIs.io
brevo Categories API
AE Profile APIs.io
brevo Contact Attributes API
AE Profile APIs.io
brevo Contact Lists API
AE Profile APIs.io
brevo Contacts API
AE Profile APIs.io
brevo Email Activity API
AE Profile APIs.io
brevo Email Campaigns API
AE Profile APIs.io
brevo Email Templates API
AE Profile APIs.io
brevo Folders API
AE Profile APIs.io
brevo Import API
AE Profile APIs.io
#Senders
← Back to B APIs
API Details
ID
brevo:brevo-senders-api
Base URL
https://api.brevo.com/v3
Docs
https://developers.brevo.com/reference
Provider
Brevo
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=brevo-senders-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/brevo-senders-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of brevo Senders API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.