- Can I use fatpanda-gmbh/bexio-connector-bundle in a Laravel application?
- Not directly. It is a Symfony bundle whose only job is to register the underlying fatpanda-gmbh/bexio-connector library in the Symfony DI container, expose a configuration tree and wire autowiring. Laravel has no equivalent bundle boot process, so a service provider, facade and publishable config are all missing, and essentially all of the bundle code is inert in a Laravel app. The practical option is to depend on the underlying SDK and wrap it yourself.
- How do I install fatpanda-gmbh/bexio-connector-bundle?
- In a Symfony project you install it with Composer, register the bundle in your kernel and add credentials under the bundle configuration key. It is not installable as a Laravel package because it ships no Laravel service provider or config publishing. Because the last release dates from June 2020, expect Composer constraint conflicts on symfony/*, Guzzle and PSR-18/17 packages before installation succeeds.
- Does this bundle support Laravel 9, 10 or 11 and PHP 8?
- No. The last release is from June 2020, which predates PHP 8, Laravel 9+ and Symfony 5.4/6/7, so its Composer constraints will likely conflict with a modern Laravel stack. Forcing installation with --ignore-platform-reqs is a warning sign rather than a fix, because the code was never tested against those runtime versions. Treat it as incompatible unless you fork and modernise it.
- What Bexio data can I access with this package?
- The wrapper exposes whatever the underlying fatpanda-gmbh/bexio-connector SDK supports, typically Swiss business data such as contacts, invoices and orders. It does not add domain mapping, idempotency, retry logic or token lifecycle management, which are usually the hard parts of a Bexio integration. You should confirm the specific endpoints you need, such as items, taxes, accounts or payments, against the connector's 2020-era coverage.
- How are Bexio API credentials configured in this bundle?
- The bundle provides a Symfony configuration tree for the credentials and endpoints expected by the SDK. In Laravel there is no equivalent config surface out of the box, so you would need to create your own config file and bind the client in a service provider. You also own token storage and refresh, because the bundle does not manage the OAuth2 lifecycle for you.
- Is fatpanda-gmbh/bexio-connector-bundle still maintained?
- No. The last release was published on 2020-06-02, the repository has roughly one star and no dependents, and it is maintained by a single author with no visible issue activity. There is effectively no security patching path and no support contract. For a package that touches statutory accounting data, that is a compliance and audit concern, not just an engineering one.
- Which Bexio authentication method does this connector use?
- The SDK behind this bundle was written in 2020, so it may target an older Bexio auth model than the OAuth2 flows and personal API tokens Bexio uses today. You must verify which auth mode the client actually implements before relying on it. If you proceed, plan to own token storage, refresh and revocation yourself, especially for multi-tenant OAuth2.
- What are the alternatives for integrating Bexio into Laravel?
- The two realistic paths are forking the underlying SDK and modernising it, or building a thin typed client with Laravel's HTTP client or a package like Saloon for the ten to twenty endpoints you actually use. Building thin is often cheaper because you avoid stale framework constraints and gain control over retries, idempotency and mapping. Either way, wrap the client behind an anti-corruption layer and queue outbound sync jobs.
- Can I test the Bexio integration safely before production?
- Use the Bexio sandbox environment and mock HTTP responses in your own test suite, because the bundle and underlying SDK do not give you reliable test or CI guarantees from 2020. Write contract tests for the endpoints you depend on and assert mapping, retries and idempotency behaviour. Do not assume the package's original tests still pass or cover your use cases.
- What production risks come with using this bundle?
- The main risks are abandonment, API drift against Bexio's current endpoints and auth, Composer conflicts with modern PHP and Laravel, and the absence of a support or security patching path. For accounting records you also need to answer who is the system of record, how reconciliation works and what Swiss VAT, CHF and retention rules apply. Review these with finance and legal before committing.