Pushover notifications channel for Laravel

This package makes it easy to send Pushover notifications with Laravel Notifications.

Installation
- Setting up your Pushover account
Usage
- Available Message methods
Changelog
Testing
Security
Contributing
Credits
License

Installation

You can install the package via composer:

composer require laravel-notification-channels/pushover

Setting up your Pushover account

To start sending messages via Pushover, you have to register an application. Add the generated Pushover application token to the services config file:

// config/services.php
...
'pushover' => [
    'token' => 'YOUR_APPLICATION_TOKEN',
],
...

Usage

Now you can use the channel in your via() method inside the notification as well as send a push notification:

use NotificationChannels\Pushover\PushoverChannel;
use NotificationChannels\Pushover\PushoverMessage;
use Illuminate\Notifications\Notification;

class AccountApproved extends Notification
{
    public function via($notifiable)
    {
        return [PushoverChannel::class];
    }

    public function toPushover($notifiable)
    {
        return PushoverMessage::create('The invoice has been paid.')
            ->title('Invoice paid')
            ->sound('incoming')
            ->lowPriority()
            ->url('http://example.com/invoices', 'Go to your invoices');
    }
}

Make sure there is a routeNotificationForPushover method on your notifiable model, for instance:

...
public function routeNotificationForPushover()
{
    return $this->pushover_key;
}

If you want to specify specific devices, you can return a PushoverReceiver object.

...
public function routeNotificationForPushover() {
    return PushoverReceiver::withUserKey('pushover-key')
        ->toDevice('iphone')
        ->toDevice('desktop')
        // or, if you prefer:
        ->toDevice(['iphone', 'desktop']);
}

If you want to (dynamically) overrule the application token from the services config, e.g. because each user holds their own application token, return a PushoverReceiver object like this:

...
public function routeNotificationForPushover() {
    return PushoverReceiver::withUserKey('pushover-key')
        ->withApplicationToken('app-token');
}

You can also send a message to a Pushover group:

...
public function routeNotificationForPushover() {
    return PushoverReceiver::withGroupKey('pushover-group-key');
}

Available Message methods

Please note that only the message content is mandatory, all other methods are optional. The message content can be set via content(''), via the create method PushoverMessage::create('') or via the constructor new PushoverMessage('').

Method	Description
`content($message)`	Accepts a string value for the message text.
`html()`	Sets the message type to HTML.
`monospace()`	Sets the message type to monospace.
`plain()`	Sets the message type to plain text, this is the default.
`title($title)`	Accepts a string value for the message title.
`time($timestamp)`	Accepts either a `Carbon` object or a UNIX timestamp.
`url($url[, $title])`	Accepts a string value for a supplementary url and an optional string value for the title of the url.
`sound($sound)`	Accepts a string value for the notification sound.
`image($image)`	Accepts a string value for the image location (either full or relative server path or a URL). If there is any error with the file (too big, not an image) it will silently send the message without the image attachment.
`priority($priority[, $retryTimeout, $expireAfter])`	Accepts an integer value for the priority and, when the priority is set to emergency, also an integer value for the retry timeout and expiry time (in seconds). Priority values are available as constants
`lowestPriority()`	Sets the priority to the lowest priority.
`lowPriority()`	Sets the priority to low.
`normalPriority()`	Sets the priority to normal.
`highPriority()`	Sets the priority to high.
`emergencyPriority($retryTimeout, $expireAfter)`	Sets the priority to emergency and accepts integer values for the retry timeout and expiry time (in seconds).