Pushcut API Changes?

Pushcut
1

Recently I’ve noticed some broken things with my pushcut api calls.

Not sure when it happened, but it seems like you reference notifications in the request body not by “identifier” but by “id” now. I’ve only noticed recently since my calls to “cancel” notifications hasn’t been clearing them out from my phone (not sure how long that’s been happening though, I often just “clear all” on iOS).

Also, going through the documentation trying to figure things out, I noticed that the api url has changed from:
https://api.pushcut.io/[key]/[call]

to

https://api.pushcut.io/v1/[call]

with the “API-Key” in the header instead.

I couldn’t get the new version to work in my shortcuts, so I stuck with the old url call. But given the “/v1/” I imagine that a change is coming…

Just a heads up for anyone noticing any strangeness

2

There are two different methods of calling the Pushcut API;

  1. The “full” API, which is documented here: Web API | Pushcut . These are the https://api.pushcut.io/v1/[call] or https://api.pushcut.io/v2/[call] routes.
  2. The “webhook” API, which exposes a subset of the API in a manner that’s easier to use from some Automation tools (where configuring a POST request can sometimes be poorly-supported). This is the https://api.pushcut.io/[key]/[call] path.

Regarding identifier vs id, it is intended to be id but we’ve mis-documented it in some places and so we support both.

Could you elaborate on the issue you’re having using the API?