notification removal

Stops workingSeptember 29, 2027in 327 daysSubscribe to Firebase Cloud MessagingShare

Calls to the /iid/notification endpoint will fail on September 29, 2027. Firebase Cloud Messaging will decommission this endpoint alongside all InstanceId server APIs and the device group feature. Any requests relying on device group management through this endpoint will no longer work after that day.

Calls it hits

/iid/notification

What to use instead of these calls

Send to each FCM registration token with POST /v1/projects/{project}/messages:send instead of using a device group. Because device groups have no direct replacement, your code must maintain its own list of registration tokens and send to each one.

Device groups have no replacement: the code must keep its own list of registration tokens and send to each.

In Firebase Cloud Messaging's words

All the InstanceId server APIs and the device group feature are deprecated and will be decommissioned on September 29, 2027.

Firebase Cloud Messaging, Announcement

Facts

API: Firebase Cloud Messaging fcm.googleapis.com
Kind: Removal
Announced: September 1, 2026
Takes effect: September 29, 2027
Calls after that day: Fail
Source: Announcement
Last updated: October 23, 2026
Verified: November 6, 2026, against Firebase Cloud Messaging's own pages

Questions

When does this change take effect?

Calls to /iid/notification on Firebase Cloud Messaging stop working on September 29, 2027.

What happens to calls after September 29, 2027?

They fail from that day.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix before September 29, 2027.

Add to GitHub