- Is splash/sendinblue a Laravel package or a Symfony bundle?
- Despite being listed among Laravel and PHP packages, splash/sendinblue is a Symfony bundle maintained under the SplashSync/Brevo-Bundle repository. It ships no Laravel service provider, facade, or publishable config, so it will not auto-register in a Laravel application. Treat it as a Symfony bundle that only fits a Laravel codebase through a bridge layer or by running Splash as a separate service.
- How do I install splash/sendinblue with Composer?
- Install it like any other Composer dependency with composer require splash/sendinblue, then register the bundle in a Symfony kernel. In a Laravel app there is no package:discover entry to lean on, so installation alone will not wire anything up. You also need the SplashSync core package and endpoint credentials before the connector does anything useful.
- Which Brevo or Sendinblue API objects does this bundle actually support?
- The bundle is a SplashSync connector, so it exposes whatever Brevo objects Splash maps for synchronization, typically contacts and lists rather than the full API surface. Campaigns, templates, transactional email, and webhooks should not be assumed unless you verify them in the source. Review the connector's object mapping definitions before planning workflows on top of it.
- Does splash/sendinblue support Brevo transactional email and SMS?
- The package blurb mentions transactional email and SMS, but the technical reality is a narrow Splash-synchronized surface focused on contacts and lists. Transactional email is the highest-value Brevo capability for most product teams and is the first thing to confirm in the code. If it is out of scope, use a dedicated Brevo SDK instead of this connector.
- What SplashSync core package and version does this bundle require?
- The bundle presumes the SplashSync core framework: connector registration, object mapping, and sync configuration all live there. Check its composer.json for the exact Splash core constraint and confirm that Splash itself is actively maintained. The real integration cost is the Splash dependency, not the Brevo connector.
- Which PHP and Symfony versions does splash/sendinblue support?
- Version constraints are defined in the bundle's composer.json and should be pinned along with a committed lockfile. Verify PHP, Symfony major version, and the transitive Guzzle or HTTP client version independently, since all three affect compatibility. Laravel's bundled Symfony components rarely satisfy full bundle registration requirements on their own.
- Does splash/sendinblue use the legacy Sendinblue v2 API or the current Brevo v3 endpoints?
- The package name still references Sendinblue, the pre-rebrand identity, which raises the question of whether the embedded client targets deprecated api.sendinblue.com v2 endpoints or current Brevo v3. Because the HTTP client is vendored inside the bundle, API drift will not surface as a Composer update, only as a runtime failure. Confirm the target API version before building on it, and plan a fork-and-patch or early exit if it is legacy.
- How do I configure the Brevo API key and Splash endpoint credentials?
- Configuration requires a Brevo API key plus Splash endpoint credentials, and it is handled through Symfony bundle configuration rather than Laravel config files. In a Laravel host you would need to supply these values yourself through an adapter or environment bridge. There is no config publishing command to fall back on.
- Can I use splash/sendinblue as a standalone Brevo SDK without SplashSync?
- Not practically. The Brevo client is embedded for SplashSync synchronization rather than exposed as a general-purpose SDK, and there is no service provider or standalone entry point. Using it in isolation means either running Splash as a sidecar service and integrating over HTTP or queue, or writing an adapter the vendor does not maintain. A dedicated Brevo PHP SDK is usually the lower-risk choice.
- Is splash/sendinblue actively maintained, and what are the Laravel alternatives for Brevo?
- Adoption signals are weak: zero stars, zero dependents, single-vendor maintenance by SplashSync, and no visible CI, test coverage, or security scanning. The MIT license is clean, but maintenance cadence and support commitments are unverified. For Laravel projects needing Brevo, evaluate a general-purpose Brevo or Sendinblue PHP SDK, or the official API directly, rather than a Splash-specific connector.