List email campaigns with the Brevo API

Lists the email campaigns, newest first by default. The response has campaigns and count; page with limit and offset. Statistics come back only when statistics is sent.

Identifier
brevo_list_email_campaigns

The request

POST https://connect.reportei.com/api/tools/brevo_list_email_campaigns/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "type": "classic"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
typestringNoOnly campaigns of this type.Values: classic, trigger
statusstringNoOnly campaigns in this status.Values: suspended, archive, sent, queued, draft, inProcess, inReview, cancelling, cancelled
statisticsstringNoStatistics to include. They cover only the last 6 months; for older campaigns use Get email campaign.Values: globalStats, linksStats, statsByDomain
startDatestringNoOnly campaigns sent from this date-time. Requires endDate, works only without status or with status sent, and the range is up to 2 years.
endDatestringNoOnly campaigns sent up to this date-time. Requires startDate.
excludeHtmlContentbooleanNotrue leaves the HTML of each campaign out of the response.
sortstringNoOrder of creation. The default is desc.Values: asc, desc
limitintegerNoCampaigns per page, up to 100. The default is 50.
offsetintegerNoIndex of the first campaign of the page. The default is 0.

Supported connections

Your customer connects their Brevo account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/brevo_list_email_campaigns. It becomes your agent's tool definition with no conversion.

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.