Weave Code
Salesmanago Api Bundle Laravel Package
pixers/salesmanago-api-bundle
A PHP bundle that integrates the SalesManago marketing automation API into your application, providing ready-made service wrappers for managing contacts, events, and email marketing data without writing raw HTTP calls yourself.
Symfony bundle that integrates with SalesManago
Frequently asked questions about Salesmanago Api Bundle
- Can I use pixers/salesmanago-api-bundle in a Laravel application?
- Not directly. This is a Symfony bundle built around a Bundle class, a DependencyInjection extension, and YAML/XML service definitions, none of which exist in Laravel. Installing it via Composer in a Laravel app gives you no service provider, no facade, and no publishable config, so nothing wires up. Treat it as a reference implementation and port the API logic rather than adopting it as a dependency.
- Is this a Laravel package or a Symfony bundle?
- It is a Symfony bundle, despite often being listed alongside Laravel packages. Its integration surface is AppKernel registration, a configuration tree parsed by a DI extension, and container service definitions. There is no composer.json extra.laravel block and no Laravel service provider. That mismatch is the single biggest reason to avoid it in a Laravel codebase.
- How do you install and configure it in Symfony?
- You register the bundle in AppKernel, import its service definitions, and supply SalesManago API credentials through the bundle's configuration tree. The container then exposes a client service you inject where needed. All of that is Symfony-specific plumbing that has no equivalent in Laravel.
- Does it support Laravel 10, 11, or 12 and PHP 8.2+?
- No. The last release was 2016-08-17, which points to Symfony 2.8/3.x, PHP 5.6/7.0, and Guzzle 5/6 constraints. Those conflict with modern Laravel versions and PHP 8.2+. Expect Composer dependency resolution failures before you even reach runtime issues.
- What SalesManago operations does the bundle actually cover?
- The bundle ships service wrappers for SalesManago contacts, events, and marketing data operations, so you avoid writing raw HTTP calls yourself. That coverage reflects the 2016 API surface, including contact upsert, event tracking, and email or funnel triggers. What it supports today is unverified, because SalesManago's endpoints, auth flow, and consent fields have likely moved on.
- Is pixers/salesmanago-api-bundle still maintained?
- No. The last release was in August 2016, roughly nine years ago, and the repository has about one star and zero dependents. It originated as an internal extraction at Pixers, a poster-printing e-commerce company, not a community project. With no dependents, nobody is filing issues, patching bugs, or validating it against the current SalesManago API.
- What is the best alternative for a Laravel integration with SalesManago?
- Build a thin first-party client over SalesManago's current documented API using Guzzle or Saloon, wrapped in a Laravel service provider with a config file and facade. That gives you the lowest long-term cost because you own the contract but not the framework glue. If SalesManago publishes an official PHP SDK, prefer that over a nine-year-old bundle.
- How would I port this bundle to Laravel if I need its SalesManago quirks?
- Fork it privately, lift the request builders and response DTOs, and replace the DI extension with a Laravel service provider, config file, and facade. This is the right path when the bundle encodes non-obvious SalesManago behavior such as auth token refresh, pagination, or error envelopes. Budget it as a multi-day spike plus a build, not a composer require.
- How does the bundle handle API credentials and GDPR consent data?
- Credentials are injected through the Symfony container configuration, which is the part you would have to rewrite for Laravel. SalesManago is EU and Poland hosted and processes contact PII and consent state, so you must verify where consent flags are handled against your DPA and data-residency requirements. The 2016 code predates many current consent and data-protection fields.
- What license does the bundle use, and can I fork it safely?
- It is BSD-3-Clause, so forking is permitted as long as you keep the copyright notice and attribution in your repository. The real risk is ownership: you would be maintaining a fork with no upstream to merge from. If you only need endpoint contracts, auth flow, and payload shapes, read the source and reimplement instead of forking.
Weaver
How can I help you explore Laravel packages today?