Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Laximo Laravel Package

shude/laximo

Laravel/PHP integration for the Laximo automotive parts catalog API. It wires Laximo services into Laravel, provides configurable API access, and helps query vehicle, catalog, and part information for fitment and lookup features.

Deep Wiki
Context7

LaximoOEM API Library

Frequently asked questions about Laximo
How do I install shude/laximo in a Laravel application?
Install it with Composer using composer require shude/laximo. Laravel package discovery should register the service provider, after which you publish and configure the package settings. Consult the package README for the exact publish command and configuration keys.
What Laximo API credentials and configuration does shude/laximo require?
The package is described as configurable for Laximo API credentials and endpoint settings. Expect to provide your Laximo login or key and any required endpoint, locale, or environment values in the published config file. Confirm the exact required keys in the package README before going live.
Which Laravel versions does shude/laximo support?
The provided overview does not list supported Laravel versions. Check the package composer.json and README for version constraints before installing. Verify compatibility with your application's Laravel and PHP versions in a staging environment.
How do I look up vehicles and catalogues with shude/laximo?
shude/laximo wraps Laximo web-service calls and provides methods for common catalogue and vehicle lookup workflows. You use the resolved client to query vehicles and catalogues, then build parts-search features on top of the responses. Refer to the README or source for exact method names and response shapes.
Can shude/laximo be used to search for parts and fitment information?
The package is intended for vehicle, catalogue, and part information lookup, which supports fitment and parts-search features. It wraps the Laximo API rather than storing catalogue data itself, so results depend on your Laximo subscription and API responses. Confirm method coverage in the package source or README.
How is the Laximo client resolved from Laravel's service container?
The overview says the package includes Laravel service container integration. Typically you resolve the client through dependency injection or app() using the package binding after configuring credentials. Check the service provider for the exact binding and whether a facade is provided.
How do I test Laximo API calls in a Laravel app using shude/laximo?
You can test your application code by mocking the Laximo client or binding a fake implementation in Laravel's container. The package overview does not describe built-in test doubles, so verify what it exposes. Avoid hitting the live Laximo API in automated tests and use recorded fixtures where possible.
Is shude/laximo suitable for production parts-search features?
It is framework-friendly and configurable, but production suitability depends on your Laximo plan, rate limits, and error handling. Review how the client handles timeouts, failures, and caching before using it in a live parts search. Add monitoring and fallbacks around external API calls.
What are alternatives to shude/laximo for Laximo integration in PHP?
Alternatives include calling the Laximo API directly with a custom client or using other Laximo SDKs or wrappers available on Packagist. Compare configuration style, Laravel integration, and method coverage against your needs. If you need only a few endpoints, a lightweight custom service may be simpler.
How do I maintain or extend shude/laximo if the Laximo API changes?
Because the package wraps the Laximo web service, API changes may require updates to client methods or configuration. Review the repository and issue tracker for maintenance activity, and consider forking if you need long-term control. Add integration tests around the endpoints you depend on.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console