404 error when calling push on valid push tokens

[Gaurav Rai]

Hi,

We have a service which pushes to using the WebPush API using push tokens received from the browser. These tokens are collected using the PushManager browser interface.

In one of our recent pushes we saw a large number of push tokens return a 404. Some of the tokens that have been working since 2021 also gave the same error. The error looks like this:

A valid push subscription endpoint should be specified in the URL as such: https://fcm.googleapis.com/wp/dHIoDxE7Hdg:APA91bH1Zj0kNa...

Does the migration to HTTPv1 API require a change in a setup where push tokens are pushed directly? Is there a way to migrate these failing push tokens?

Thanks