- Does mpp/apicil-client-bundle work with Laravel?
- Not out of the box. It is a Symfony bundle with a DI extension, service definitions, and a configuration tree, and there is no Laravel service provider, facade, or publishable config. In Laravel you should treat it as a third-party SDK, bind it as a singleton in your own service provider, and expose it only through your own ApicilGateway interface.
- How do I install mpp/apicil-client-bundle with Composer?
- Require mpp/apicil-client-bundle via Composer and pin to 3.3.2 or later within 3.3.x rather than floating. Before installing, check the package's composer.json for PHP, Symfony, and PSR version bounds against your application. The release history suggests patch-level semantic versioning, but you should still audit transitive constraints yourself.
- What is an arbitrage operation in the Apicil API?
- An arbitrage is a contractual write operation on a policy, typically a reallocation or switch of investment supports on a life-insurance or capitalisation contract. It is not a read-only call, so your integration needs idempotency, confirmation, and audit semantics. Model it as a domain command with an explicit result or status object rather than raw HTTP.
- How do I register the Apicil client in a Laravel service provider?
- Bind the client as a singleton in a dedicated service provider and configure it from config/services.php plus .env values instead of hard-coding credentials. Wrap the vendor client in your own ApicilGateway interface so no Apicil DTO or Symfony exception crosses into your domain layer. Keep the package confined to a single adapter directory under your app.
- Does the Apicil client support idempotency for arbitrage writes?
- The available documentation does not state whether arbitrage creation is idempotent or accepts a client-supplied reference. Because arbitrage is a transactional operation, verify this with the vendor before relying on it. If it is not idempotent, add your own request reference, confirmation step, and reconciliation against the returned operation reference.
- Which authentication method does the Apicil API use?
- The bundle description does not specify the auth model; plausible options include OAuth2 client credentials, an API key, or mTLS. You also need credentials from Apicil under commercial or contractual terms, so partner access is the real gate, not the code. Confirm the API version, auth flow, and sandbox availability during diligence.
- Is mpp/apicil-client-bundle safe to use in production?
- Treat it cautiously. It has zero stars, zero dependents, a low quality score, and a single originating organisation, so bus factor is one. Positive signs include an active PR history and the 3.3.2 patch, but no SLA, changelog, CI status, or security posture is proven. Isolate it behind an adapter and pin the version.
- What PHP and Laravel versions does mpp/apicil-client-bundle support?
- Its composer.json should be checked for PHP, Symfony, and PSR constraints; there are no Laravel constraints because it is a Symfony bundle. Confirm those bounds are compatible with your Laravel release and your PHP runtime. There is no official Laravel version support statement.
- How do I test an Apicil API integration in Laravel?
- The bundle advertises injectable services that can be mocked, but its own test coverage of the arbitrage write path is unproven. In Laravel, fake your ApicilGateway interface in unit tests and use HTTP fakes only if the underlying client is PSR-18 compatible. If it hard-codes Symfony HttpClient, you may need a thin transport abstraction to make testing practical.
- Are there alternatives to mpp/apicil-client-bundle for Laravel?
- You can build a thin adapter over the Apicil REST API using a PSR-18 client, or consume a framework-agnostic core client if one exists, rather than depending on the Symfony bundle. Before choosing, check which endpoints are covered beyond arbitrage and whether retries, timeouts, and error mapping are declared or left to the caller. Partner access and credentials remain the main constraint either way.