Weave Code
Laravel Bexio Laravel Package
codebar-ag/laravel-bexio
Laravel Bexio by codebar AG offers a fluent, Laravel-friendly integration with the Bexio Swiss business software API, letting you manage contacts, invoices, orders, and accounting data through a clean, expressive interface backed by Eloquent-style models.
Laravel Bexio is a Laravel integration for the Bexio API, the Swiss business software for invoicing, accounting, and CRM. It provides a clean, expressive wrapper around Bexio's REST endpoints so you can manage contacts, invoices, and other resources directly from your Laravel application using familiar Eloquent-style syntax.
- Seamless Laravel service provider and facade integration
- Fluent methods for contacts, invoices, and orders
- Built-in OAuth2 authentication handling
- Publishable configuration for tokens and settings
- Easy installation via Composer and well-documented usage
Frequently asked questions about Laravel Bexio
- What is codebar-ag/laravel-bexio used for?
- It is a Laravel package that wraps the Bexio API in a convenient client plus publishable configuration, so you can read and write Swiss business data such as contacts, invoices, and orders from your application. Instead of hand-rolling HTTP calls, you resolve the package's client from Laravel's service container and work with a consistent API surface. It is aimed at Laravel applications that already use Bexio as their accounting or ERP backend.
- How do I install laravel-bexio with Composer?
- Run composer require codebar-ag/laravel-bexio and let Composer resolve the version against your locked dependencies. Because the package is a Laravel package, it is typically registered through package auto-discovery via extra.laravel.providers, so no manual provider registration is normally required. After installing, publish the config file with the vendor:publish command referenced in the repository and add your Bexio API credentials. Commit the composer.lock change so every environment resolves the same version.
- Which Laravel and PHP versions does laravel-bexio support?
- The package is released as v14.0.0, and the authoritative support matrix lives in its composer.json require and require-dev sections rather than in prose. Before scheduling work, read those constraints and confirm your host application's Laravel major and minimum PHP version fall inside them. If they do not, treat the work as a framework upgrade with the package as a passenger, not as a simple package install. Also check whether any sibling package pins an older major of this one, since Composer will surface that conflict at resolution time.
- How do I configure the Bexio API credentials in Laravel?
- Publish the package config file and place your Bexio client credentials in your .env file, mapping them through the published config keys. Keep secrets out of version control and set them per environment, including staging and CI. If your application uses config caching, run php artisan config:clear followed by config:cache after changing values. Confirm the token or OAuth credentials have the scopes needed for the endpoints you call, since Bexio will reject requests otherwise.
- How do I fetch contacts or create invoices using the Bexio client?
- Resolve the package client or facade from the container and call the resource methods for contacts, invoices, or orders as documented in the repository. Bexio expects specific payload shapes and country or currency codes, so validate your request data before sending it and log the raw response for debugging. Wrap calls in try/catch and handle rate limiting and non-2xx responses explicitly. Integration tests against a sandbox or mocked HTTP layer will catch payload regressions faster than manual testing.
- Does v14 of laravel-bexio contain breaking changes and how should I upgrade?
- Under semantic versioning, a major bump to v14 signals a non-backward-compatible contract change, and the published release notes are empty, so the diff has to be reconstructed from the repository and tag comparison. The safer path is a staged upgrade: pin your current version, confirm the suite is green, move to the latest v13.x and clear deprecation warnings, then read the v13 to v14 diff and write a short internal change summary before branching to v14. Upgrade behind a feature flag and run your full suite plus a staging smoke test. Avoid jumping straight from an older major, or you risk stacking two majors of drift into one untraceable failure.
- Can I test Bexio API calls without hitting the real Bexio API?
- You should, because hitting a live accounting system from a test suite is both slow and destructive. Mock the HTTP layer your Laravel version provides, or bind a fake implementation of the client behind the container binding the package exposes, and assert on the outgoing payloads. Keep a small number of opt-in integration tests against a Bexio test tenant for the endpoints you depend on. Feature-flag the call sites so the package can be disabled in environments without credentials.
- Is laravel-bexio safe to use in production?
- The main risk is information asymmetry rather than mechanics: the v14 release ships without notes, so the scope of breaking changes, database impact, and deprecations is unconfirmed. Before production use, verify whether the release introduces or alters migrations, config keys, facade aliases, or service-container bindings, since a migration-bearing major can require a backfill or two-phase deploy. Check that transitive dependency bumps resolve against your locked versions. Then roll out by environment, or by tenant if you are multi-tenant, rather than all at once.
- What are the alternatives to laravel-bexio?
- You can call the Bexio REST API directly with Laravel's HTTP client and a small service class of your own, which removes a dependency but means maintaining auth, pagination, and error handling yourself. Other options are a generic Bexio SDK wrapped in a Laravel service provider, or a different community Laravel wrapper if one is actively maintained. Evaluate alternatives on Laravel version support, release cadence, and the maintainer's responsiveness to issues, not just on feature lists.
- Who maintains laravel-bexio and how disciplined is its release process?
- The package is published by codebar-ag on GitHub, and the repository is the place to check maintainer activity, issue response times, and tag history. The v14.0.0 release currently has empty release notes, which is a signal worth raising with the maintainer: ask for the breaking-change list, the v13 to v14 upgrade guide, the supported Laravel and PHP matrix, and how long v13 will receive fixes. Those answers, plus the bus factor behind the project, should inform whether you pin tightly and budget discovery work for each major.
Weaver
How can I help you explore Laravel packages today?