Get contact with the Brevo API

Returns one contact with its attributes, lists and the campaign statistics of the last 90 days.

Identifier
brevo_get_contact

The request

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

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "identifier": "<identifier>"
  }
}

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
identifierstringYesEmail address, contact id or SMS number of the contact. Other identifiers need identifierType.
identifierTypestringNoWhat identifier is. Required for ext_id, whatsapp_id and landline_number_id.Values: email_id, phone_id, contact_id, ext_id, whatsapp_id, landline_number_id

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_get_contact. 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.