In 4.x there is no Configuration object. Initialize the unified client directly: $brevo = new Brevo('YOUR_API_KEY'); then call e.g. $brevo->transactionalEmails->sendTransacEmail(...). If you cannot migrate yet, pin composer.json to the 2.x line, but the team recommends moving to the modern client. R…
This is a serializer bug in the v4 SDK: it never matched "bool" against gettype()'s "boolean". It was fixed in v4.0.10, which adds an explicit is_bool() check in JsonSerializer.php mirroring the existing is_float() workaround. Upgrade with composer require getbrevo/brevo-php:^4.0.10 and boolean valu…
This is an SDK bug, not your code: v4.0.7 tries to JSON-decode success responses that can be empty or non-JSON. It was fixed in v4.0.11, where the SDK handles those responses gracefully instead of throwing during deserialization. Upgrade with composer require getbrevo/brevo-php:^4.0.11 and the excep…
In 4.x there is no Configuration object. Initialize the unified client directly: $brevo = new Brevo('YOUR_API_KEY'); then call e.g. $brevo->transactionalEmails->sendTransacEmail(...). If you cannot migrate yet, pin composer.json to the 2.x line, but the team recommends moving to the modern client. R…
This is a serializer bug in the v4 SDK: it never matched "bool" against gettype()'s "boolean". It was fixed in v4.0.10, which adds an explicit is_bool() check in JsonSerializer.php mirroring the existing is_float() workaround. Upgrade with composer require getbrevo/brevo-php:^4.0.10 and boolean valu…
This is an SDK bug, not your code: v4.0.7 tries to JSON-decode success responses that can be empty or non-JSON. It was fixed in v4.0.11, where the SDK handles those responses gracefully instead of throwing during deserialization. Upgrade with composer require getbrevo/brevo-php:^4.0.11 and the excep…