- How do I install unicodeveloper/jusibe-php-lib in a Laravel application?
- Install it with composer require unicodeveloper/jusibe-php-lib. There is no Laravel service provider, facade or publishable config, so nothing is auto-discovered and there is no artisan install step. You instantiate the client yourself, passing your Jusibe API keys, and keep those credentials in config/services.php and your .env file. Before committing, run a composer why-not check against your PHP and Laravel versions because the package has not been updated since 2020.
- Is unicodeveloper/jusibe-php-lib a Laravel package?
- No. It is a framework-agnostic PHP REST wrapper around the Jusibe SMS gateway and has no service provider, facade, notification channel, queue-aware job or config file. In a Laravel codebase it behaves like raw vendor SDK code, which means vendor DTOs and error semantics leak into controllers and jobs if you call it directly. The sensible pattern is to place it behind your own SmsSender contract and keep the Jusibe client as the only implementation detail.
- Does jusibe-php-lib support PHP 8.2, PHP 8.3 and Laravel 10 or 11?
- Support is unverified. The last release was 2020-07-14, and its legacy Guzzle constraints are the most likely source of conflicts with Laravel's bundled HTTP client and with modern framework upgrades. Validate with composer why-not and a full composer update --dry-run inside a clean Laravel skeleton before adoption. If a version constraint is the only blocker, the MIT license makes a fork or a VCS repository entry a pragmatic fix, but that turns an external dependency into internal code you must own.
- How do I send an SMS to multiple recipients with this library?
- The wrapper advertises sending SMS messages to either a single recipient or multiple recipients through its send call, so you pass the recipient numbers according to the method signature in the source. The client handles authentication and the HTTP request, and returns the API response for you to interpret. Because the exact method names are not documented in the package description, read the class source once and wrap the call in your own adapter so the signature never spreads through your codebase.
- How do I fake or mock jusibe-php-lib in Laravel tests?
- You almost certainly cannot use Http::fake() because the library issues requests through its own transport rather than an injectable Laravel HTTP client. Mock at an adapter boundary instead: define an internal SmsSender contract with plain DTOs, bind a fake or spy implementation in the container during tests, and let the Jusibe adapter be the only file that imports vendor classes. For integration coverage, record and replay responses against a Jusibe test account or sandbox.
- How do I check my remaining Jusibe SMS credits from PHP?
- The library includes a call that queries your Jusibe account balance and returns the remaining SMS credits. Avoid hitting it on every page request; cache the value for a short window and expose it through a small internal service rather than calling the vendor client from a controller. If the balance call fails, decide explicitly whether to fail the send or log and continue.
- Does this library support delivery status webhooks or idempotency keys?
- The wrapper can retrieve delivery status for messages you have already sent, but webhook support and idempotency keys are not part of its documented surface. Assume neither exists and confirm with Jusibe whether delivery receipts can be pushed to an endpoint you own. For safe retries, generate your own client reference, send through a queued job with backoff, and de-duplicate on that reference before handing anything to the gateway.
- Is unicodeveloper/jusibe-php-lib still maintained?
- Signals are weak. The last release was 2020-07-14, the repository has roughly 34 stars, and there is no visible maintainer succession or recent PHP major-version patch. Expect composer audit and software composition analysis tooling to flag it, and plan for an internal owner who is willing to fork it under the MIT license if a security or compatibility fix is needed.
- What are the alternatives to jusibe-php-lib for sending SMS in Laravel?
- The strongest alternative is no library at all: call the Jusibe REST endpoints directly with Laravel's Http client, which gives you Http::fake() in tests, retry and timeout handling, and no legacy Guzzle constraints. You can also evaluate maintained notification channel packages for other Nigerian gateways, or a generic SMS notification channel behind the same SmsSender contract. Keeping the contract in place means swapping providers later is a contained change rather than a refactor.
- Where should Jusibe API keys live in a Laravel project?
- Store them in your .env file and expose them through config/services.php, since the package ships no config of its own to publish. Never commit the keys, and cache your configuration in production so the values are read once. Because credentials and message content flow through a third party, also confirm Jusibe's data residency, DPA posture and sender-ID registration requirements before going live.