Brevo · Schema
getSmtpTemplateOverview
MarketingMarketing AutomationEmail MarketingTransactional EmailSMS MarketingWhatsAppCampaignsCRMSalesE-CommerceLoyaltyEventLive ChatEmailSMSAutomationMessagingContacts
Properties
| Name | Type | Description |
|---|---|---|
| createdAt | string | Creation UTC date-time of the template (YYYY-MM-DDTHH:mm:ss.SSSZ) |
| doiTemplate | boolean | It is true if template is a valid Double opt-in (DOI) template, otherwise it is false. This field will be available only in case of single template detail call. |
| htmlContent | string | HTML content of the template |
| id | integer | ID of the template |
| isActive | boolean | Status of template (true=active, false=inactive) |
| modifiedAt | string | Last modification UTC date-time of the template (YYYY-MM-DDTHH:mm:ss.SSSZ) |
| name | string | Name of the template |
| replyTo | string | Email defined as the "Reply to" for the template |
| sender | object | |
| subject | string | Subject of the template |
| tag | string | Tag of the template |
| testSent | boolean | Status of test sending for the template (true=test email has been sent, false=test email has not been sent) |
| toField | string | Customisation of the "to" field for the template |
| customTemplateId | string | Custom template identifier, if one was assigned during template creation. Only present when the template has a custom ID. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/brevo/main/json-schema/brevo-get-smtp-template-overview-schema.json",
"title": "getSmtpTemplateOverview",
"x-generated": "2026-10-12",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/brevo-transactional-emails-api-openapi.yml#/components/schemas/getSmtpTemplateOverview",
"type": "object",
"properties": {
"createdAt": {
"type": "string",
"description": "Creation UTC date-time of the template (YYYY-MM-DDTHH:mm:ss.SSSZ)"
},
"doiTemplate": {
"type": "boolean",
"description": "It is true if template is a valid Double opt-in (DOI) template, otherwise it is false. This field will be available only in case of single template detail call."
},
"htmlContent": {
"type": "string",
"description": "HTML content of the template"
},
"id": {
"type": "integer",
"format": "int64",
"description": "ID of the template"
},
"isActive": {
"type": "boolean",
"description": "Status of template (true=active, false=inactive)"
},
"modifiedAt": {
"type": "string",
"description": "Last modification UTC date-time of the template (YYYY-MM-DDTHH:mm:ss.SSSZ)"
},
"name": {
"type": "string",
"description": "Name of the template"
},
"replyTo": {
"type": "string",
"format": "email",
"description": "Email defined as the \"Reply to\" for the template"
},
"sender": {
"$ref": "#/$defs/GetSmtpTemplateOverviewSender"
},
"subject": {
"type": "string",
"description": "Subject of the template"
},
"tag": {
"type": "string",
"description": "Tag of the template"
},
"testSent": {
"type": "boolean",
"description": "Status of test sending for the template (true=test email has been sent, false=test email has not been sent)"
},
"toField": {
"type": "string",
"description": "Customisation of the \"to\" field for the template"
},
"customTemplateId": {
"type": "string",
"description": "Custom template identifier, if one was assigned during template creation. Only present when the template has a custom ID."
}
},
"required": [
"createdAt",
"htmlContent",
"id",
"isActive",
"modifiedAt",
"name",
"replyTo",
"sender",
"subject",
"tag",
"testSent",
"toField"
],
"$defs": {
"GetSmtpTemplateOverviewSender": {
"type": "object",
"properties": {
"email": {
"type": "string",
"format": "email",
"description": "From email for the template"
},
"id": {
"type": "string",
"description": "Sender id of the template"
},
"name": {
"type": "string",
"description": "Sender name for the template"
}
},
"title": "GetSmtpTemplateOverviewSender"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/brevo-get-smtp-template-overview"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.