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

Brevo Transactional Whats App API

The transactionalWhatsApp API from Brevo — 2 operation(s) for transactionalwhatsapp.

Brevo Transactional Whats App 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.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and an AsyncAPI specification.

This API exposes 2 operations across 2 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

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

2 operations 2 paths 11 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Brevo Transactional Whats App API declares 1 security scheme for authenticating requests. An API key is passed in the header as api-key (api-key).

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

Paths & Operations 2

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

transactionalWhatsApp 2
POST
/whatsapp/sendMessage
Send a WhatsApp message
sendWhatsappMessage 1 param body → 201400
GET
/whatsapp/statistics/events
Get all your WhatsApp activity (unaggregated events)
getWhatsappEventReport 9 params → 200400

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are WhatsappStatisticsEventsGetResponsesContentApplicationJsonSchemaEventsItems (8 properties), GetWhatsappEventReportRequestBadRequestError (2 properties), SendWhatsappMessageRequestBadRequestError (2 properties), Transactional_WhatsApp_sendWhatsappMessage_Response_201 (1 property). Each schema is shown below with its type and property counts.

WhatsappStatisticsEventsGetParametersEvent
string
Transactional_WhatsApp_getWhatsappEventReport_Response_200
object
1 property
WhatsappSendMessagePostResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
WhatsappStatisticsEventsGetResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
Transactional_WhatsApp_sendWhatsappMessage_Response_201
object
1 property 1 required
WhatsappStatisticsEventsGetParametersSort
string
SendWhatsappMessageRequestBadRequestError
object
2 properties 2 required
GetWhatsappEventReportRequestBadRequestError
object
2 properties 2 required
WhatsappStatisticsEventsGetResponsesContentApplicationJsonSchemaEventsItemsEvent
string
Event which occurred
WhatsappStatisticsEventsGetResponsesContentApplicationJsonSchemaEventsItems
object
8 properties 5 required
Transactional_WhatsApp_sendWhatsappMessage_Request

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

brevo-transactionalwhatsapp-api-openapi.yml Raw ↑

Other APIs Brevo publishes across the network.

brevo Agent Status API
brevo Automated Messages API
brevo Campaign Statistics API
brevo Categories API
brevo Contact Attributes API
brevo Contact Lists API
brevo Contacts API
brevo Email Activity API
brevo Email Campaigns API
brevo Email Templates API
brevo Folders API
brevo Import API
Where this information came from

This is an independent, third-party profile of Brevo Transactional Whats App 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.