Weave Code
Laravel Notification Zapmizer Laravel Package
zapmizer/laravel-notification-zapmizer
A Laravel notification channel for Zapmizer that lets you send notifications through Zapmizer's API using Laravel's built-in notification system. Configure credentials, route recipients, and deliver messages cleanly from your application.
A Laravel package to send WhatsApp notifications using Zapmizer API
Frequently asked questions about Laravel Notification Zapmizer
- How do I install zapmizer/laravel-notification-zapmizer?
- Install it with Composer using composer require zapmizer/laravel-notification-zapmizer. Laravel package auto-discovery should register the service provider, then publish any included config file if the README instructs you to. Because the underlying Zapmizer SDK is pre-1.0, pin the version you test with in composer.json.
- How do I configure the Zapmizer WhatsApp channel in Laravel?
- Configuration is handled through the package's published config and Laravel's notification channel setup, so you add your Zapmizer credentials and defaults there. Keep credentials in environment variables and cache config in production. Check the README for the exact config keys because the package wraps a pre-1.0 SDK and config names can change.
- How do I send a WhatsApp notification with Zapmizer in Laravel?
- Add the Zapmizer channel to your notification's via() array and define the channel-specific message payload as shown in the package README. Then send the notification through Laravel's normal Notification facade or notifiable trait. The package handles delivery through Zapmizer's gateway.
- Which Laravel and PHP versions does laravel-notification-zapmizer support?
- The authoritative support matrix is the require section of the package's composer.json and the README. The provided package context does not list exact Laravel or PHP versions, so verify before upgrading. Since the underlying SDK is pre-1.0, test against your Laravel version and pin a known-good release.
- How does this package handle WhatsApp rate limits and 429 responses?
- The underlying Zapmizer SDK exposes MediaRateLimitedException for 429-style rate limiting and includes retryAfter() accessors, and awaitMedia() can wait on Retry-After before resuming. In a Laravel notification channel, avoid blocking request or worker time; move retries into queued jobs with backoff aligned to retryAfter(). Keep a cap on wait time and monitor worker occupancy.
- What should I do when Zapmizer rejects media in a notification?
- The SDK throws MediaRejectedException for rejected media and MediaRateLimitedException for rate-limited media, both extending ZapmizerConnectException. Catch the specific exceptions at a boundary adapter and return a domain result such as Rejected or Deferred. Let 422-style rejection propagate to a user-facing validation outcome, and treat 429 as retryable.
- Can I send Zapmizer notifications from a Laravel queue worker?
- Yes, notifications can be queued like any Laravel notification, but be careful with media waits. The SDK's awaitMedia() may wait on Retry-After, so run it in a dedicated job with explicit timeout, retryUntil, and backoff rather than inside a synchronous request. Ensure the job timeout exceeds any bounded wait and that retries are limited.
- How do I test Laravel notifications that use the Zapmizer channel?
- Use Laravel's Notification::fake() to assert the notification was sent without hitting Zapmizer, and add contract tests around your adapter for the SDK's 422 and 429 exceptions. If you call awaitMedia(), fake or stub the client so tests do not sleep on Retry-After. Assert that MediaRejectedException maps to a rejection result and MediaRateLimitedException maps to a deferred or retry result.
- Is zapmizer/laravel-notification-zapmizer production-ready?
- It is a small integration layer, but it depends on a pre-1.0 SDK, so treat the no-breaking-changes guarantee as a courtesy rather than a contract. Pin versions, wrap vendor exceptions in one internal adapter, and add tests for rate-limit and media-rejection paths. The main operational risk is blocking waits in awaitMedia(), which should be bounded and moved to queued jobs.
- What are alternatives to this package for WhatsApp notifications in Laravel?
- Alternatives include other Laravel notification channels for WhatsApp providers or building a thin adapter around a provider's HTTP API yourself. If you already use Zapmizer, this package saves you from writing the channel plumbing. Evaluate alternatives on Laravel version support, rate-limit handling, media support, and whether the SDK is stable enough for production.
Weaver
How can I help you explore Laravel packages today?