Weave Code
Movesms Laravel Package
savannabits/movesms
Laravel integration for the MoveSMS SMS gateway, providing a simple API to send text messages, check delivery reports and manage SMS credits from your PHP applications.
PHP Laravel Adapter for fluently interacting with the Movetech Bulk SMS API
Frequently asked questions about Movesms
- What is savannabits/movesms used for?
- It is a PHP Laravel adapter for fluently interacting with the Movetech Bulk SMS API. It gives Laravel applications a simple way to send text messages, check delivery reports and manage SMS credits through the MoveSMS gateway. It is intended as a thin integration layer rather than a full notification or marketing platform, so you still drive sending logic from your own application code.
- How do I install savannabits/movesms in a Laravel application?
- The expected path is a standard Composer install, followed by Laravel package auto-discovery of the service provider. If the package publishes a configuration file, you would run the vendor publish command and then set your MoveSMS credentials. Note that the exact install steps, config file name and facade alias are not documented in the available release data, so verify them against the repository README before wiring it in.
- Which PHP versions does savannabits/movesms support?
- The v1.0.0 release note states support for PHP 8.0 and PHP 8.1. That is the only documented compatibility signal available, and it implies the package was authored in the Laravel 8/9 era. PHP 8.2, 8.3 and 8.4 are not validated, and PHP 8.0 is already end of life while 8.1 security support ends in December 2025.
- Which Laravel versions can I use with savannabits/movesms?
- The Laravel version constraint is not documented in the available data, which is a real gap for planning. If the illuminate/* requirements are pinned to ^8.0 or ^9.0, installation on Laravel 10 or 11 will fail at dependency resolution rather than at runtime. Check the composer.json constraints before committing to it, and treat Laravel 8/9 as the presumptive fit.
- Can I use savannabits/movesms on PHP 8.2 or PHP 8.3?
- There is no validated support path for PHP 8.2 or newer in the v1.0.0 release information. Running unvalidated code on newer runtimes risks deprecation noise and, for reflection or serialization heavy code, subtle breakage. If your target services run PHP 8.2 or 8.3, treat this package as out of fit until it publishes a broader test matrix, or test it thoroughly behind your own adapter.
- How do I send an SMS with savannabits/movesms?
- The package is described as a fluent API for the MoveSMS gateway, so sending is expected to be a short chain of calls on the package's client or facade after credentials are configured. The exact method names and payload shape are not enumerated in the supplied release data, so confirm the signature from the repository source or README. Because the public surface is undocumented, wrap your send call in a small internal service class so a future API change is a one-file edit.
- How do I configure my MoveSMS API credentials?
- MoveSMS credentials are typically supplied through a publishable config file backed by environment variables, which is the standard Laravel package convention. The available release data does not confirm the config key names or whether a config file is published at all. Never commit credentials to version control; keep them in your .env and, where multi-tenant, resolve them per tenant rather than globally.
- Does savannabits/movesms support delivery reports and credit balance checks?
- Yes, the package description explicitly covers checking delivery reports and managing SMS credits alongside sending messages. These are pull-style calls against the Movetech API, so you would typically schedule them or trigger them from a job rather than blocking a user request. The precise response shape is undocumented, so normalise the results into your own DTOs before storing them.
- Is savannabits/movesms production ready and well maintained?
- It is at v1.0.0 with a single documented release note, so semver guarantees and release cadence are unproven. Maintainer identity, governance, issue response record and support policy are all unknown from the available data, which makes for a real bus-factor risk. For anything in a critical notification path, isolate it behind an internal interface and be prepared to fork or swap the driver.
- Should I adopt savannabits/movesms or write my own Laravel SMS client?
- Movetech's bulk SMS API is largely commoditized, so set the build-versus-adopt bar high: ask whether this package unlocks something you could not do in roughly two engineer-days yourselves. If you do adopt it, bind it behind a thin internal adapter from day one so a fork or replacement is a swap rather than a refactor. Also confirm the license terms and transitive dependency footprint before the go/no-go decision.
Weaver
How can I help you explore Laravel packages today?