Weave Code
Api Bundle Laravel Package
keboola/api-bundle
Keboola API Bundle is a Symfony bundle for building consistent JSON APIs, providing reusable request handling, validation, standardized error responses, and extension points for authentication, logging, and documentation. It helps teams standardize endpoint behavior and reduce boilerplate across PHP...
A lightweight Symfony bundle for integrating the Keboola API into PHP applications. It provides framework-native service configuration so Keboola clients can be injected and used through Symfony’s dependency injection container without manual wiring.
- Registers Keboola API services in the Symfony container
- Configurable credentials, endpoints, and client options
- Works with Symfony DI autowiring and standard bundle configuration
- Extensible foundation for Keboola platform API integrations
Frequently asked questions about Api Bundle
- Is keboola/api-bundle compatible with Laravel?
- No, not natively. It is a Symfony bundle that relies on Symfony's dependency injection container, HttpKernel, Config component, and bundle registration model. There is no Laravel service provider, facade, publishable config, or Artisan surface, so any Laravel usage requires a custom integration layer or an anti-corruption adapter.
- How do I install keboola/api-bundle in a Laravel app?
- You generally should not install it as a drop-in dependency. Its Symfony component constraints may collide with the symfony/* packages Laravel already locks, so run a Composer why-not analysis first. Audit the repository to see whether transport, auth, pagination, retries, and DTOs live in the bundle or in a separate Keboola client library.
- Does keboola/api-bundle include a Laravel service provider or facade?
- No. The package has no Laravel service provider, facade, publishable configuration, or Artisan commands. Its wiring is Symfony bundle registration, so Laravel bindings, credential configuration, and error mapping must be written by your team if you choose to integrate it.
- What Keboola APIs and authentication models does it support?
- The provided context does not enumerate the exact Keboola APIs or auth models. You should verify in the repository whether it covers Storage, Connection, or Manage APIs and whether it uses Storage API tokens, Master tokens, or OAuth. Do not assume coverage until you audit the source and its dependencies.
- Is there a standalone Keboola PHP client I should use instead?
- Audit composer.json for a separate dependency such as keboola/php-api-client. If transport, authentication, pagination, retries, and DTOs live there, depend on that library directly and skip the Symfony bundle. The bundle is likely thin Symfony glue, so a native Saloon or Guzzle client against the Keboola REST API is often the lower-risk default.
- What Laravel and PHP versions are supported by keboola/api-bundle?
- There is no documented Laravel support matrix. The bundle pins Symfony component ranges that may conflict with Laravel 10, 11, or 12 on PHP 8.2+, so Composer constraint collisions are a gating step. Check composer why-not against your exact Laravel and PHP versions before committing to integration.
- Can I use keboola/api-bundle in production?
- Only conditionally. Adoption signals are weak, with zero stars, zero dependents, no visible community, and single-vendor support. The 2026-10-08 release date is anomalous relative to the current date, which undermines confidence in release hygiene. Isolate it behind an interface, pin versions, and keep a raw HTTP fallback.
- How should I test a Keboola integration in Laravel?
- Start with a spike that authenticates against a Keboola sandbox project and executes one read plus one job-creation flow. Wrap the client behind a KeboolaClientContract and use contract tests with a fake implementation. If the bundle cannot be constructed outside a booted Symfony kernel, test it as a separate Symfony sidecar over HTTP or a queue.
- What are alternatives to keboola/api-bundle for Laravel?
- The main alternatives are a direct Saloon or Guzzle client against Keboola's REST API, a standalone Keboola PHP client library, or running the Symfony bundle as a sidecar service. The preferred pattern is a domain contract with a thin adapter or native HTTP implementation. Avoid making the Symfony bundle a core Laravel dependency.
- Is keboola/api-bundle actively maintained?
- Maintenance signals are weak. The repository is marked READ-ONLY, has zero stars and dependents, and shows no visible community or support surface. The anomalous 2026 release date and undocumented backward-compatibility guarantees suggest you should treat it as vendor code, pin versions, and budget for a fork if needed. The MIT license permits forking but transfers maintenance cost to you.
Weaver
How can I help you explore Laravel packages today?