- How do I install smsapi.pl/php-client in a Laravel application?
- Install it with composer require smsapi.pl/php-client. The package is a plain PHP SDK with no service provider, config file or facade, so installation only adds vendor code plus its PSR HTTP dependencies. You then construct the client yourself with your SMSAPI.pl credentials, typically inside a service class or a container binding in a service provider you write. Run composer why-not against your lockfile first to catch any PSR-7 version conflict.
- Does this package ship a Laravel service provider or facade?
- No. The technical evaluation confirms there is no service provider, no configuration file and no facade, so nothing is auto-discovered or publishable. That keeps vendor code at the edge of your domain, but it means your team owns the glue: a singleton binding, a config entry for the API token, and a thin wrapper class. Budget a small amount of wiring work rather than expecting a drop-in Laravel package.
- Which Laravel and PHP versions does smsapi.pl/php-client support?
- The SDK imposes no framework-version constraints of its own, so Laravel compatibility comes down to your PHP floor and its PSR dependency versions. It fits PHP 8.x applications on Laravel 10, 11 or 12 comfortably. The most likely friction is a PSR-7 major-version disagreement with packages already pinned in your composer.lock, so verify with composer why-not before committing.
- How do I send an SMS from a Laravel queued job or notification?
- Construct the client with your credentials in a service class, inject that service into the job or notification, and call the message-sending action from there. Because the package is queue-agnostic, you get retries, backoff and failed-job handling by dispatching the send from a queued job instead of the request cycle. Keep the SDK call inside a small wrapper so the rest of your code depends on your interface rather than the vendor class.
- Does it support bulk SMS campaigns and delivery reports?
- The documented API surface covers bulk sending, delivery status polling and inbound message retrieval, which maps onto typical campaign and transactional use cases. What the evaluation could not confirm is whether delivery reports arrive as callbacks or only as synchronous send responses, so check the source before designing a status-tracking table. If only polling is available, schedule a job to reconcile statuses rather than blocking a request.
- Can I inject my own HTTP client for logging, tracing and timeouts?
- The dependency tree is largely PSR HTTP abstractions, and the open question flagged in the evaluation is whether the client accepts PSR-18 injection. If it does, you can route traffic through your existing Guzzle stack and gain logging, tracing, retries and timeouts without touching SDK internals. Verify it in the constructor signature before building middleware assumptions into your architecture.
- How does the client surface errors, and can I tell retryable failures from terminal ones?
- This is one of the unresolved questions in the technical evaluation: it is not documented here whether the SDK throws typed exceptions or returns raw HTTP responses. Read the client source and its exception classes to see how HTTP 4xx and 5xx responses propagate. Once known, map retryable conditions into your job's retry logic and let terminal failures fail fast so you do not pay for repeated sends.
- What licence does smsapi.pl/php-client use, and can I use it commercially?
- The repository declares NOASSERTION, which is a licence-detection failure rather than a clear permissive grant. Before the package enters a commercial codebase, have legal confirm the actual licence text, including whether closed-source commercial use and redistribution inside a Docker image are permitted. A package that cannot state its terms is a procurement blocker, not a code-quality nit.
- Is smsapi.pl/php-client actively maintained and safe for production?
- It is a first-party SDK published by the gateway vendor, so it is maintained because their business depends on it rather than because of community momentum. Health signals are thin: roughly 66 GitHub stars and zero dependents mean little community troubleshooting, and the reported last release date of 2026-04-09 should be verified rather than taken as proof of active maintenance. Expect to read the source when something goes wrong.
- Can I use this client if we are not already an SMSAPI.pl customer, or if we send outside Poland?
- If SMSAPI.pl is already your contracted provider, integration feasibility is high and this SDK is the natural choice. If this evaluation is really a provider-selection decision, the SDK's quality is secondary to pricing, deliverability and coverage. Note also that the package is Poland-focused: sender-name registration and Polish/EU marketing-consent rules carry locality assumptions that will not transfer if the product expands to other markets.