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 Sms API

The transactionalSms API from Brevo — 4 operation(s) for transactionalsms.

Brevo Transactional Sms 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 Transactional SMS. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and an AsyncAPI specification.

This API exposes 4 operations across 4 paths, and defines 21 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.

4 operations 4 paths 21 schemas 3 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 Sms 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 4

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

transactionalSms 4
POST
/transactionalSMS/send
Send SMS message asynchronously to a mobile number
sendAsyncTransactionalSms 1 param body → 201400
GET
/transactionalSMS/statistics/aggregatedReport
Get your SMS activity aggregated over a period of time
getTransacAggregatedSmsReport 5 params → 200400
GET
/transactionalSMS/statistics/reports
Get your SMS activity aggregated per day
getTransacSmsReport 6 params → 200400
GET
/transactionalSMS/statistics/events
Get all your SMS activity (unaggregated events)
getSmsEvents 10 params → 200400

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are TransactionalSmsStatisticsReportsGetResponsesContentApplicationJsonSchemaReportsItems (11 properties), Transactional_SMS_getTransacAggregatedSmsReport_Response_200 (11 properties), sendTransacSms (10 properties), TransactionalSmsStatisticsEventsGetResponsesContentApplicationJsonSchemaEventsItems (7 properties). Each schema is shown below with its type and property counts.

GetTransacSmsReportRequestBadRequestError
object
2 properties 2 required
SendTransacSmsTag
Tag of the message. Can be a single string or an array of strings (maximum 10 tags). Each tag must be a non-empty string.
Transactional_SMS_sendAsyncTransactionalSms_Response_201
object
1 property 1 required
TransactionalSmsStatisticsEventsGetParametersEvent
string
Transactional_SMS_getTransacAggregatedSmsReport_Response_200
object
11 properties
TransactionalSmsStatisticsEventsGetResponsesContentApplicationJsonSchemaEventsItems
object
7 properties
GetSmsEventsRequestBadRequestError
object
2 properties 2 required
Transactional_SMS_getSmsEvents_Response_200
object
1 property
sendTransacSms
object
10 properties 2 required
GetTransacAggregatedSmsReportRequestBadRequestError
object
2 properties 2 required
TransactionalSmsSendPostResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
TransactionalSmsStatisticsEventsGetResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
TransactionalSmsStatisticsReportsGetResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
TransactionalSmsStatisticsEventsGetResponsesContentApplicationJsonSchemaEventsItemsEvent
string
Event which occurred
TransactionalSmsStatisticsAggregatedReportGetResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
SendTransacSmsType
string
Type of the SMS. Marketing SMS messages are those sent typically with marketing content. Transactional SMS messages are sent to individuals and are triggered i…
TransactionalSmsStatisticsReportsGetResponsesContentApplicationJsonSchemaReportsItems
object
11 properties
TransactionalSmsStatisticsEventsGetParametersSort
string
TransactionalSmsStatisticsReportsGetParametersSort
string
Transactional_SMS_getTransacSmsReport_Response_200
object
1 property
SendAsyncTransactionalSmsRequestBadRequestError
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

brevo-transactionalsms-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 Sms 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.