Weave Code
Notification Api Client Bundle Laravel Package
idci/notification-api-client-bundle
A Symfony bundle that provides an API client for the IDCI Notification service, letting PHP applications send and manage notifications through a simple, configurable integration.
Symfony2 notification client api bundle
Frequently asked questions about Notification Api Client Bundle
- Can I install idci/notification-api-client-bundle in a Laravel application with Composer?
- You can run composer require, but nothing will be auto-discovered the way a Laravel package is. The package is a Symfony bundle: it relies on a Bundle class registered in config/bundles.php, a DependencyInjection extension, and a Configuration tree, none of which Laravel recognises. There is no ServiceProvider and no config file merge, so you would have to register and boot the services yourself. In practice that means bootstrapping a minimal Symfony container alongside Laravel's or bypassing the bundle entirely.
- Is this bundle compatible with recent Laravel versions?
- There is no first-class Laravel support at any version, so the question is really whether the underlying Symfony components conflict with what Laravel already pulls in. Symfony bundle conventions changed materially across Symfony 4, 5, 6 and 7, and an unmaintained bundle stays pinned to whichever major it targeted. Check the composer.json constraints before assuming anything, and expect to work around dependency resolution rather than solve it.
- What licence does the package use, and can I ship it in a commercial product?
- The package is GPL-3.0, which is copyleft. Internal-only Laravel applications are generally fine, and SaaS use is usually tolerable, but shipped binaries, on-premise appliances, or client-delivered code can carry obligations that are expensive to unwind later. For most product integrations this alone is a reason to stop at the gate. If you need it, ask the vendor whether a permissive licence is obtainable.
- Does the bundle contain a framework-agnostic client I can use without Symfony?
- That is the critical unknown and it can only be answered by reading the source. Small, older bundles often wrap raw HTTP calls in Symfony service definitions rather than exposing a standalone SDK, in which case the client logic is inseparable from the container wiring. If the request-building classes do separate cleanly, you can depend on the underlying package and instantiate the client manually from a Laravel ServiceProvider. If they do not, the realistic path is reimplementation, not integration.
- How do I call the IDCI notification API from Laravel without using the bundle?
- Extract the request-building logic from the source: endpoint, auth scheme, headers, payload schema and response parsing. Then write a small NotificationClient in your app that uses Laravel's Http facade, with credentials and base URL bound from config/services.php. The package is small enough to audit in an afternoon, so this is usually cheaper than importing Symfony's DependencyInjection and Config components for what is functionally an HTTP client.
- Is this package actively maintained?
- Adoption signals are effectively zero: a couple of stars and no dependents means no external community has found or fixed edge cases. It is a single-vendor package from IDCI Consulting, most likely published for their own internal use, with no evidence of release cadence, issue triage or a support commitment. Check the latest commit date and latest tagged release before deciding anything.
- Which Symfony versions does the bundle support?
- You need to read the composer.json constraints, because that is where the answer lives. Symfony changed bundle API conventions significantly across majors, and an unmaintained bundle pins you to the major it targeted. That pin can conflict with Symfony components Laravel already pulls in transitively, so verify resolution in a scratch project before touching your real application.
- How do I test notification sending in a Laravel app that uses this API?
- Do not let tests hit the live service. If you wrap the client behind an interface resolved from the container, you can bind a fake in your test case and assert on the payloads it receives. If you reimplement the client on Laravel's Http facade, Http::fake gives you request assertions and canned responses with no extra tooling. Either way, keep the endpoint and credentials in config so tests can override them.
- What alternatives should I consider for sending notifications in Laravel?
- Laravel's own notification system already covers mail, database, broadcast and SMS-style channels, and it is the natural first stop. If you specifically need the IDCI notification service, use a thin Guzzle or PSR-18 client against its REST API and skip the Symfony bundle. If the upstream service is IDCI's own product and not a public API, confirm it is still live before building anything around it.
- What should I verify before depending on this bundle?
- Confirm whether a standalone, non-Symfony client for the same API is published separately, and what the notification API actually is: a specific vendor's REST service or IDCI's own product. Check that the upstream API is still live, along with the latest commit date, latest tagged release, and the PHP and Symfony constraints in composer.json. Finally, determine whether the package does anything beyond request signing and serialization, and whether that logic is non-trivial or API-specific enough to justify porting it.
Weaver
How can I help you explore Laravel packages today?