- Is routmoute/routmoute-sirene-bundle compatible with Laravel?
- Not natively. The package is built as a Symfony bundle with a DI extension and service definitions, and there is no Laravel ServiceProvider or publishable config out of the box. You can still consume its framework-agnostic client and DTO classes inside a Laravel app, but you will need to bind and configure them yourself in a service provider. Check the composer.json require block first to confirm nothing pulls in Symfony framework packages you do not want.
- How do I install routmoute/routmoute-sirene-bundle?
- Install it with Composer using composer require routmoute/routmoute-sirene-bundle and pin ^1.1.1 explicitly rather than floating ^1.1.0, which likely shipped a stale default API URL. In Symfony you then register the bundle in bundles.php so the DI extension loads. In Laravel you would skip bundle registration and instantiate the client manually or via your own container binding.
- How do I configure SIRENE API credentials for this bundle?
- Configuration is handled through the bundle's DI extension, so credentials live in your Symfony config and environment variables rather than in code. The services are then autowired and ready to inject. Before relying on it, verify whether the package performs INSEE OAuth2 client-credentials and token refresh itself or expects a pre-fetched bearer token from your application.
- Does routmoute-sirene-bundle support SIREN, SIRET and company search lookups?
- Yes. It exposes a typed client service for the SIRENE v3 endpoints covering search, siren and siret lookups, plus full establishment records. Responses are mapped to DTOs instead of raw arrays, which keeps your calling code clean. The HTTP transport is PSR-18 and PSR-17 compatible, so you can plug in a client that already has your proxy, retry and telemetry middleware.
- Which PHP and Symfony versions does routmoute-sirene-bundle require?
- That is unverified from the release notes, so read the composer.json require block before committing. Check the PHP constraint against your runtime matrix and the Symfony or Guzzle HTTP package ranges against your existing HTTP stack. A version mismatch there can turn a small bundle into a dependency-resolution problem.
- How should I test a SIRENE API integration without hitting production?
- Spike it in a scratch application: resolve the client, call the search endpoint with an INSEE sandbox key, and confirm the configured URL actually responds. There is no evidence of a bundled test suite or CI in the release history, so plan to write your own contract tests against the sandbox. Wrapping the vendor behind an internal CompanyLookup interface lets you fake responses in unit tests.
- Is routmoute/routmoute-sirene-bundle actively maintained?
- It appears to be a single-maintainer project with low activity; version 1.1.1 was only the third pull request and changed a default API URL constant. There is no visible CI, test coverage or stated support window in the release notes. Treat it as a small utility you should be prepared to fork or replace, and keep your own abstraction around it.
- Why did version 1.1.1 change the SIRENE API URL in a patch release?
- The change updates a default API_URL constant, most plausibly in response to an INSEE endpoint migration or deprecation. Because it landed as a patch, a routine composer update could silently redirect production traffic if you never overrode the URL yourself. Pin ^1.1.1, diff the old and new defaults, and confirm any config file you own still points at a live endpoint before promoting.
- Should I use this bundle or write my own INSEE SIRENE client?
- The package is thin: a config block, an HTTP client wrapper and DTO mapping, roughly a couple hundred lines of logic. If you are on Laravel or need control over retries, proxies, telemetry and OAuth2 token handling, a single Guzzle client behind your own interface is often simpler and removes the framework-binding risk entirely. Choose the bundle when you are on Symfony and want autowired services with minimal setup.
- What are the alternatives to routmoute-sirene-bundle for French company data?
- You can call the INSEE SIRENE v3 API directly with Guzzle or symfony/http-client, or use another community SIRENE or INSEE client package. Whatever you pick, define an internal CompanyLookup port and keep the vendor swappable, since the upstream government API and its deprecation schedule are outside your control. Also confirm the license and maintenance posture before adopting.