Weave Code
Fabriq Connector Laravel Package
karabinse/fabriq-connector
Fabriq Connector is a Laravel/PHP integration package that provides a clean, configurable bridge between your application and Fabriq services, simplifying setup and service wiring while keeping Fabriq-specific logic out of your codebase.
At a glance
Frequently asked questions about Fabriq Connector
- How do I install Fabriq Connector in a Laravel app?
- Install it with Composer using composer require karabinse/fabriq-connector. The package ships a service provider and facade that Laravel registers automatically through package discovery, so no manual wiring is usually required. After installation, publish the configuration file and add your Fabriq credentials to your .env file before making your first request.
- Do I need to publish the config file, and what settings does it contain?
- Publishing the config file is the supported way to customize the package, and you can do it with Laravel's vendor:publish command. It holds the Fabriq endpoints, credentials, and timeout values that the client reads at runtime. Keep the actual secret values in environment variables and reference them from the config so nothing sensitive lands in version control.
- Which Laravel versions does Fabriq Connector support?
- The package is built for modern Laravel applications and relies on the framework's service provider, facade, and configuration systems. Because exact version constraints can change between releases, check the require block in the package's composer.json or the support matrix in the README before upgrading your framework. Composer will also tell you immediately if your installed Laravel version conflicts with the package constraint.
- How does authentication and credential management work?
- Credentials are supplied through the publishable config file, which reads its values from environment variables. That keeps API keys and secrets out of your source code and lets each environment use its own Fabriq account. You can also override the config values at runtime if you need to talk to a different tenant or staging endpoint.
- How do I send a request to Fabriq with the fluent client?
- You interact with Fabriq through the provided facade, which resolves the underlying client from the container. Requests are expressed fluently and return typed responses, so you work with predictable objects rather than decoding raw JSON by hand. This removes the need to write boilerplate Guzzle or HTTP client code for each endpoint.
- How are API errors and failed responses handled?
- Error handling is built on Guzzle's transport layer, so connection problems, timeouts, and non-successful HTTP responses surface as exceptions you can catch. That lets you handle failures in one place instead of checking status codes after every call. Wrap Fabriq calls in try/catch blocks and log the exception context when a request fails in production.
- Can I fake the Fabriq client when writing tests?
- Yes. The package is designed to be test-friendly, with dependency injection and fakes supported so you can swap the real client for a stub in your test suite. That means your feature and unit tests never hit the live Fabriq API and stay fast and deterministic. Resolve the client from the container in your own code so the fake can be bound in tests.
- How do I change the timeout or point the package at a different endpoint?
- Both are config-driven. Edit the published config file or set the matching environment variables to change the base endpoint or the request timeout. This makes it straightforward to run against a sandbox or staging Fabriq instance while production keeps its own settings.
- Why use Fabriq Connector instead of calling the Fabriq API with Laravel's HTTP client directly?
- Calling the API directly works, but you end up repeating authentication, URL building, and response decoding in every part of your codebase. This package centralizes that into a configurable client with typed request and response handling, which keeps Fabriq-specific logic out of your domain code. It also gives you a single seam for faking responses in tests, which is harder to do cleanly with ad hoc HTTP calls.
- Is the package actively maintained and how do I keep it up to date?
- The package is versioned on Packagist and installed through Composer, so composer update karabinse/fabriq-connector pulls in the latest release. Before upgrading, review the changelog on the GitHub repository for configuration or API changes. Because it wraps an external platform, keeping it current matters when Fabriq changes its endpoints or authentication requirements.
Weaver
How can I help you explore Laravel packages today?