Connect Brevo

How Brevo signs requests

Brevo reads your API key from the api-key header on every request.

Can you connect it today?

Yes. Add an API-key-in-a-header credential with the header name api-key.

A sample mapping

Your application sends the first request below. The mapping turns it into the body of POST /v3/contacts, shown second.

{
    "email": "ana@example.com",
    "phone": "+351912345678"
}

{
    "email": "ana@example.com",
    "attributes": {
        "SMS": "+351912345678"
    }
}

The mapping

{
    "$schema": "https://schemas.echorelay.dev/transform/mapping/v1.json",
    "root": {
        "type": "object",
        "id": "root",
        "properties": {
            "email": {
                "type": "field",
                "id": "email",
                "path": "email"
            },
            "attributes": {
                "type": "object",
                "id": "attributes",
                "properties": {
                    "SMS": {
                        "type": "field",
                        "id": "sms",
                        "path": "phone"
                    }
                }
            }
        }
    }
}

The grammar, the answer mapping and the dry run are in the mapping docs.

What you bring

This is not a ready-made connector. You bring a sample request or Brevo’s OpenAPI document, you or your agent write the mapping, and we run the integration you define.