Firebase Cloud Messaging
Device group management on /gcm/notification removal
Stops workingSubscribe to Firebase Cloud MessagingShare
On September 29, 2027, device group management on /gcm/notification will be decommissioned. Calls to the /gcm/notification endpoint will fail after that day. Firebase Cloud Messaging announced that all InstanceId server APIs and device groups are deprecated.
Calls it hits
/gcm/notification
What to use instead of these calls
Send to each FCM registration token using POST /v1/projects/{project}/messages:send instead of a device group. Because device groups have no direct replacement, your code must maintain its own list of registration tokens and dispatch to each one individually.
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 /gcm/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
-
/fcm/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.