PHPackages                             fernleafsystems/apiwrappers-pushover - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. fernleafsystems/apiwrappers-pushover

ActiveLibrary

fernleafsystems/apiwrappers-pushover
====================================

PHP Wrapper For The Pushover Notifications API

1.0.0(3y ago)0302↓100%MITPHPPHP >=7.4.0

Since Nov 24Pushed 3y ago1 watchersCompare

[ Source](https://github.com/FernleafSystems/ApiWrappers-Pushover)[ Packagist](https://packagist.org/packages/fernleafsystems/apiwrappers-pushover)[ RSS](/packages/fernleafsystems-apiwrappers-pushover/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependencies (1)Versions (7)Used By (0)

ApiWrappers-Pushover
====================

[](#apiwrappers-pushover)

PHP Wrapper for Pushover Notifications API

Installation
------------

[](#installation)

To get started, add the package to your project by issuing the following command:

```
composer require fernleafsystems/apiwrappers-pushover

```

Current version 0.1.x is beta. Please include using strict Composer versions.

Getting Started
---------------

[](#getting-started)

Only 2 main parts of the API are implemented so far:

1. User/Group Verification
2. Message sending (`Push`ing)

### 1) User / Group Verification

[](#1-user--group-verification)

With all API requests, the first thing to do is create a new API Connection.

**Verify a user or a group**

```
	use FernleafSystems\ApiWrappers\Pushover;

	$oConnection = ( new Pushover\Connection() )
			->setApiKey( 'your api key' );

	$bSuccess = ( new Pushover\User\Verify() )
		->setConnection( $oConn )
		->setUserGroupKey( 'user or group key' )
		->verify();
```

### 2) User / Group Verification with changed Key

[](#2-user--group-verification-with-changed-key)

To perform actions against the API you send an Access Token - not the OAuth code you obtained in the previous stage. To get this, your app will send a request for a new token and it will look like this:

### 3) Send a message

[](#3-send-a-message)

```
	use FernleafSystems\ApiWrappers\Pushover;

	$bSuccess = ( new Pushover\Message\Push() )
		->setConnection( $oConn )
		->setUserGroupKey( 'user or group key' )
		->setTitle( 'My lovely title' )
		->setMessage( 'An important message' )
		->setIsHtml( false )
		->push();
```

Sending a message is very simple. Give the title and the message and adjust any other parameters of the Message according to the API.

### 4) Send to a specific device.

[](#4-send-to-a-specific-device)

```
	$bSuccess = ( new Pushover\Message\Push() )
		->setDevice( 'Device Key' )
		...
		->push();
```

All the current API classes let you specify an optional device. If this is omitted it uses all devices.

In the case of Verify, if it's omitted it verifies the user has at least 1 active device.

Errors and Exceptions
---------------------

[](#errors-and-exceptions)

When retrieving, creating and updating, there are some basic checks on the data to ensure the absolute minimums are provided before a request is sent out. If these checks fail an `Exception` is thrown.

If these checks don't fail, and the request fails, you have a few options. This will likely change in the future as the current implementation is flawed and not satisfactory.

If you find bugs, suggestions for improvements etc., please do let us know.

###  Health Score

30

—

LowBetter than 64% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity13

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity67

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~449 days

Total

5

Last Release

1292d ago

Major Versions

0.2.1 → 1.0.02022-10-25

PHP version history (2 changes)0.1.0PHP >=5.6.0

1.0.0PHP >=7.4.0

### Community

Maintainers

![](https://www.gravatar.com/avatar/034fb67e76a9eef20cdb667c11b591a009dbece86d0c31fd7e84cc88fa03ee52?d=identicon)[paulgoodchild](/maintainers/paulgoodchild)

---

Top Contributors

[![paulgoodchild](https://avatars.githubusercontent.com/u/10562196?v=4)](https://github.com/paulgoodchild "paulgoodchild (19 commits)")

---

Tags

notificationsApi Wrapperpushover

### Embed Badge

![Health badge](/badges/fernleafsystems-apiwrappers-pushover/health.svg)

```
[![Health](https://phpackages.com/badges/fernleafsystems-apiwrappers-pushover/health.svg)](https://phpackages.com/packages/fernleafsystems-apiwrappers-pushover)
```

###  Alternatives

[laravel/slack-notification-channel

Slack Notification Channel for laravel.

89069.7M111](/packages/laravel-slack-notification-channel)[minishlink/web-push

Web Push library for PHP

1.9k12.0M52](/packages/minishlink-web-push)[dmitrovskiy/ionic-push-php

ionic push notifications php sdk

215.5k1](/packages/dmitrovskiy-ionic-push-php)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)