Weave Code
Smsup Api Bundle Laravel Package
smsup/smsup-api-bundle
Symfony bundle for integrating the SMSUP API into PHP applications. It provides configuration and service wiring to help connect your Symfony project to SMSUP and send SMS messages with less setup.
Bundle Symfony2 para el uso de la api de smsup.es para el envio de sms
Frequently asked questions about Smsup Api Bundle
- Is smsup/smsup-api-bundle compatible with Laravel?
- No. It is a Symfony 2 bundle built around HttpKernel, DependencyInjection and services.yml conventions, with no Laravel service provider, facade or extra.laravel auto-discovery block. Laravel has no bundle loader or AppKernel registration, so it is not installable into a Laravel app in any supported sense.
- How do I install smsup/smsup-api-bundle in a Laravel project?
- You should not run composer require against a Laravel 10 or 11 app. Symfony 2-era constraints and old Guzzle versions conflict with PHP 8.1+ and current Laravel dependencies, and --ignore-platform-reqs only puts broken code on disk. If you need to inspect it, use a throwaway scratch directory and copy out the API details rather than adding it as a dependency.
- Can I use this Symfony bundle to send SMS from Laravel 10 or 11?
- Not directly, but the functional payload is small enough to reimplement. The bundle ultimately posts a destination number, sender ID and message body to smsup.es with an API key and parses a response. In Laravel you would build that transport behind an SmsSender interface using the Http facade or Guzzle 7, typically in 100 to 200 lines.
- What PHP and Symfony versions does smsup/smsup-api-bundle require?
- It targets the Symfony 2 era, with PHP constraints around 5.3 to 5.5 and likely Guzzle 3.x or 5.x plus Symfony 2.x components. Symfony 2.8 reached end of maintenance in November 2018, so the whole dependency tree is EOL. That stack is two major eras behind a modern Laravel application.
- Is smsup/smsup-api-bundle still maintained?
- There is no evidence of active maintenance. It has around 2 stars, 0 dependents and a score near 0.01, with no community triage, no security disclosure path and no recent commits. Treat it as unmaintained source material for understanding the API, not as a production dependency.
- How do I send an SMS through SMSUP from Laravel without this bundle?
- Read the bundle source in a scratch environment to extract the base URL, endpoint paths, auth header or parameter name, request fields, response shape and error codes. Then create something like App\Services\Sms\SmsupClient implementing an SmsSender interface, using Laravel's Http facade or Guzzle 7. Put the API key, sender ID and timeouts in config, and make sure logging redacts credentials.
- Does smsup/smsup-api-bundle support delivery receipts or DLR?
- That is not clear from the bundle description and needs verification against the SMSUP API documentation. SMS clients of this era often support receipts by polling rather than webhooks, and some support neither. If you need delivery confirmation, confirm the current API contract or official SDK before designing a webhook or polling job with idempotent handling.
- How should I handle errors and retries when sending SMS via SMSUP?
- Assume the old client may return status codes rather than throw exceptions, so parse the response and surface structured failures as exceptions in your Laravel implementation. Retry only clearly classified transient failures, and never blindly retry unclassified errors because duplicate sends are billable. Use a deduplication store or provider-supported idempotency key to make retries safe.
- Are there better alternatives to smsup/smsup-api-bundle for Laravel?
- Check whether SMSUP now ships an official PHP SDK, which would supersede this bundle entirely. Otherwise, a small Laravel-native client behind an interface is the most maintainable choice, optionally wrapped in a notification channel. Other SMS providers with maintained Laravel packages are also worth evaluating if you are not locked into SMSUP.
- How do I handle Spanish accented characters and SMS segment length with SMSUP?
- Accented characters can force a message from GSM-7 into UCS-2 encoding, which drops capacity from 160 to about 70 characters per segment and changes the price. Verify the client does not silently truncate the body, and measure length with a GSM-7 awareness check before sending. Decide whether to normalize characters or accept UCS-2 costs, and surface the segment count in your application.
Weaver
How can I help you explore Laravel packages today?