brevo Webhooks 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 Webhook. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.
This API exposes
6 operations
across 3 paths,
and defines 38 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.
6 operations3 paths38 schemas1 DELETE2 GET2 POST1 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 Webhooks 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 6
Across 3 paths, the API surfaces 6 operations — 1 DELETE, 2 GET, 2 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
webhooks 6
GET
/webhooks
Get all webhooks
getWebhooks3 params→ 200400
POST
/webhooks
Create a webhook
createWebhook1 parambody→ 201400
GET
/webhooks/{webhookId}
Get a webhook details
getWebhook2 params→ 200400404
PUT
/webhooks/{webhookId}
Update a webhook
updateWebhook2 paramsbody→ 204400404
DELETE
/webhooks/{webhookId}
Delete a webhook
deleteWebhook2 params→ 204400404
POST
/webhooks/export
Export webhook history
exportWebhooksHistory1 parambody→ 202400
Schemas 38
The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are getWebhook (11 properties), Webhook (8 properties), CreateWebhook (5 properties), UpdateWebhook (4 properties). Each schema is shown below with its type and property counts.
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.
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 Webhooks 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.
