- What is misaf/vendra-api used for?
- misaf/vendra-api is a Laravel integration package for the Vendra API. It provides a convenient client with configuration-driven setup so you can authenticate and make Vendra API calls without writing repetitive HTTP boilerplate. The repository is a read-only subtree split of the Vendra Modules from misaf/vendra.
- How do I install misaf/vendra-api in a Laravel application?
- Install it with Composer using composer require misaf/vendra-api. Then follow any configuration or publishing steps documented in the main misaf/vendra repository, since this package is only a subtree split. If Laravel package discovery is supported, the service provider should register automatically.
- How do I configure Vendra API credentials for Laravel?
- The package uses configuration-driven setup, so credentials are typically supplied through Laravel configuration and environment variables. Check the package config file or the main misaf/vendra documentation for the exact key names and required values. Avoid hardcoding secrets in source control and clear cached config after changes.
- Which Laravel versions does misaf/vendra-api support?
- The provided context does not list specific Laravel version constraints, so check the package composer.json for its illuminate/support requirements. Because this is a subtree split, compatibility generally follows the releases of the main misaf/vendra package. Confirm the supported PHP and Laravel versions before adding it to an existing project.
- How do I make an authenticated Vendra API call with this package?
- After configuring credentials, resolve the Vendra client through Laravel’s container and call the API methods it exposes. The package is intended to handle authentication and HTTP boilerplate so your application code stays focused on business logic. For exact method names and endpoints, refer to the main misaf/vendra documentation because this repository is a read-only split.
- Can I test Vendra API integration without calling the real API?
- If the package uses Laravel’s HTTP client internally, you can typically use Http::fake() to stub responses in your test suite. Otherwise, mock or swap the package client service in Laravel’s container. The provided context does not document package-specific test helpers, so check the main repository for recommended testing patterns.
- Is misaf/vendra-api a standalone package or part of misaf/vendra?
- It is a subtree split of the Vendra Modules from the main misaf/vendra repository. That means this repository is read-only and should not receive direct commits or pull requests. Make changes and report issues against the main misaf/vendra project instead.
- What are alternatives to using misaf/vendra-api?
- You can call the Vendra API directly with Laravel’s HTTP client or Guzzle, or use an official Vendra SDK if one exists. The main advantage of this package is its configuration-driven Laravel integration and reduced HTTP boilerplate. For a single simple endpoint, direct HTTP calls may be sufficient.
- Where should I report bugs or contribute fixes for misaf/vendra-api?
- Report bugs and submit fixes to the main misaf/vendra repository, not this read-only subtree split. The split exists to distribute the Vendra Modules package through Composer. Check the main repository’s issue tracker and contribution guidelines before opening a pull request.
- Can misaf/vendra-api be used safely in production?
- Treat it like any third-party Composer dependency: review the main misaf/vendra repository, pin a known version, and test your integration before deploying. Keep Vendra credentials in environment variables and avoid committing secrets. Because specific maturity and version-support details are not provided here, verify them against the main package documentation.