Use new FCM APIs
See original GitHub issueAs of now FCM notifications are sent to https://fcm.googleapis.com/fcm/send which is a legacy API.
Messages should be sent to current API endpoint:
https://fcm.googleapis.com/v1/{parent=projects/*}/messages:send
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Firebase Cloud Messaging REST API - Google
FCM send API that provides a cross-platform messaging solution to reliably deliver messages at no cost. Service: fcm.googleapis.com. To call ...
Read more >Firebase Cloud Messaging important REST API's - Selvaganesh
Firebase Cloud Messaging (FCM) is a cross-platform messaging solution that lets you reliably deliver messages at no cost. For use cases such as...
Read more >Firebase : Send notification with REST API - Stack Overflow
Sending Firebase Notifications is only supported from the Firebase Console. But you accomplish the same by using Firebase Cloud Messaging, which ...
Read more >Fcm - googleapis documentation
Description. Firebase Cloud Messaging API. FCM send API that provides a cross-platform messaging solution to reliably deliver messages at no cost.
Read more >Cloud Messaging | React Native Firebase
FCM is a cost free service, allowing for server-device and device-device ... For example, the React Native Alert API could be used to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

You can change the API Endpoint for FCM by setting an attribute in push notification config as follows,
What concern me is that since APIs are different they accept different parameter format.
Looking into Firebase docs seems that API v1 has a different param signature from legacy one.
There is an official guide which explains why just changing URL is not enough.