Firebase Cloud Messaging
Device group management on /fcm/notification removal
Stops workingSubscribe to Firebase Cloud MessagingShare
Calls to /fcm/notification will stop working on September 29, 2027. The device group feature is deprecated and will be decommissioned on that day. Requests made to this endpoint will fail after the shutdown date.
Calls it hits
/fcm/notification
What to use instead of these calls
Device groups have no direct replacement, so your code must maintain its own list of registration tokens. Send notifications to each individual token using POST /v1/projects/{project}/messages:send instead.
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.
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
- Verified
- , against Firebase Cloud Messaging's own pages
Questions
When does this change take effect?
Calls to /fcm/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.
More from Firebase Cloud Messaging 3
-
/gcm/notificationRemoval Stops workingin 327 days -
/iid/notificationRemoval Stops workingin 327 days -
/notificationRemoval Stops workingin 327 days
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.