Reputation: 371
Firebase Cloud Messaging: REST API responds with "INVALID_KEY"
Our push notifications work fine with the in-built tester on the firebase console website.
However when we try to use Postman to simulate a push request to fire off "our own" notification the server always returns "INVALID_KEY" Error 401.
Where is the correct Key located? So far we tested:
- Web Push public key (green are in the following image)
- Web Push private key (located in the options menu in near the green area in the image)
When using these keys in Postman (plus the required body) the previosly mentioned error is returned:
What are we doing wrong? Do we need a completely different key? Thanks in advance!
Upvotes: 2
Views: 5310
Answers (1)
Reputation: 371
Found the solution: you have to create a Legacy Setup of the Cloud Messaging API under Project Settings > Cloud Messaging.
To do so press the three dots next to "Cloud Messaging API (Legacy)" and enable the service. It then automatically sets up the environment and present the key.
Upvotes: 12
Related Questions
- Firebase messaging missing Authentication key in MongoDB trigger functions:
- Failing sending notifications using firebase cloud messaging, Python API
- The request was missing an Authentication Key with push notification in firebase
- Firebase FCM returns Unauthorized error with right server key
- Firebase Cloud Message Push Notifications giving errors
- AuthenticationError sending a notification with Firebase Cloud Messaging
- Firebase API is not sending push notifications when using the API
- Can't send push notifications using the server API
- Firebase Cloud Messaging replaced the server keys with Tokens for sending notifications/messages
- Firebase curl is "Unauthorized" with correct API key