It was working until recently. I saw someone mention about PushBullet going premium but it doesn’t look like you have to pay for API access… https://www.pushbullet.com/pro.
Here’s my log when trying to send a test message:
NzbDroneErrorPipeline Invalid request Validation failed: – Unable to send test message 9:49pm
PushBulletProxy Unable to send test message: Unable to send PushBullet notifications to all channels or devices: Unable to send PushBullet notifications to all channels or devices 9:49pm
PushBulletProxy Unable to send test message to: Sonarr: Unable to send text message: REST request failed: [403] [POST] at [https://api.pushbullet.com/v2/pushes] 9:49pm
RestSharpExtensions [POST] [https://api.pushbullet.com/v2/pushes] Failed. [Forbidden] 9:49pm
Quick update: I was able to successfully send the sample push from their API page (https://docs.pushbullet.com/#create-push) to my (non-Pro) account. Possible bug in Sonarr?
I double checked my access token and even generated a new one. And I’m not using any device ID or channel. And like I said, it worked just fine when sending from curl in a command prompt. One thing I did notice, the access token started with a “o.” where it didn’t before. Would the period cause Sonarr any trouble?
Sonarr doesn’t validate the API Key, so it shouldn’t make a difference.
According to their docs a 403 means the API key is not valid for the request, perhaps a limitation on your account? An API rate limit would get a 429 response.