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 Inbound Parsing API

The inboundParsing API from Brevo — 3 operation(s) for inboundparsing.

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

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

3 operations 3 paths 14 schemas 3 GET

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 Inbound Parsing 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 3

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

inboundParsing 3
GET
/inbound/events
Get the list of all the events for the received emails.
getInboundEmailEvents 7 params → 200400
GET
/inbound/events/{uuid}
Fetch all events history for one particular received email.
getInboundEmailEventsByUuid 2 params → 200400404
GET
/inbound/attachments/{downloadToken}
Retrieve inbound attachment with download token.
getInboundEmailAttachment 2 params → 200400404

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are Inbound_Parsing_getInboundEmailEventsByUuid_Response_200 (8 properties), InboundEventsGetResponsesContentApplicationJsonSchemaEventsItems (4 properties), InboundEventsUuidGetResponsesContentApplicationJsonSchemaAttachmentsItems (4 properties), GetInboundEmailAttachmentRequestBadRequestError (2 properties). Each schema is shown below with its type and property counts.

GetInboundEmailEventsByUuidRequestBadRequestError
object
2 properties 2 required
InboundEventsGetResponsesContentApplicationJsonSchemaEventsItems
object
4 properties 4 required
InboundEventsUuidGetResponsesContentApplicationJsonSchemaAttachmentsItems
object
4 properties
Inbound_Parsing_getInboundEmailEventsByUuid_Response_200
object
8 properties
GetInboundEmailEventsRequestBadRequestError
object
2 properties 2 required
GetInboundEmailAttachmentRequestBadRequestError
object
2 properties 2 required
InboundEventsUuidGetResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
InboundAttachmentsDownloadTokenGetResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
InboundEventsGetResponsesContentApplicationJsonSchemaCode
string
Error code displayed in case of a failure
Inbound_Parsing_getInboundEmailEvents_Response_200
object
1 property
InboundEventsUuidGetResponsesContentApplicationJsonSchemaLogsItems
object
2 properties
errorModel
object
2 properties 1 required
InboundEventsUuidGetResponsesContentApplicationJsonSchemaLogsItemsType
string
Type of the event
InboundEventsGetParametersSort
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

brevo-inboundparsing-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 Inbound Parsing 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.