Sending Push via Postman using Firebase Messaging

Question

I'm trying to use Postman to send a single Push Notification using Firebase Cloud Messaging service.

This is a working cURL command for the same purposal, on which I'm using as a reference.

curl -X POST --header "Authorization: key=<API_ACCESS_KEY>" --Header "Content-Type: application/json" https://fcm.googleapis.com/fcm/send -d "{\"to\":\"<YOUR_DEVICE_ID_TOKEN>\",\"notification\":{\"body\":\"Firebase\"} \"priority":\"10"}"

What I have done so far..

1 - Set the Headers appropriately

2- At Body , I'm using raw

{
    "to" : "<YOUR_DEVICE_ID_TOKEN>"
    , 

    "notification": {
    "body": "Firebase Cloud Message"
  }

  }

When executing, I'm getting back 401 - Unauthorized.

What's missing to correctly send the push notification?

Solution 1

The correct way to set up Authorization key at Header is

key=<API_ACCESS_KEY>

and not only

<API_ACCESS_KEY>

Silly mistake, but since this could be useful for someone for testing Firebase Messaging with Postman I'm leaving the question opened.

Solution 2

Posting FCM through POSTMAN

Body - to is token id (should be generated through instance token) write body in raw binary application/json

{
   "to": "cpa8cZPjq-w:APA91bF122f1Rnhu9v47bL
   YMajaNTHAIU5SzItDwTy9o2MCIveG0PlK78VPvp3d
   CqjwnUKZ4
   ngi1trSyM3_aXttW62iknFfbPGtjRLhZr6wq-3qFdboz8gzdOGPz**********",

   "notification": {

    "body": "Hello",
    "title": "This is test message."
   }
   }

header: should have authorization :server key

Content type : application/json after posting here the success message:

Solution 3

Open Postman, click on Enter request URL textbox, enter firebase url

https://fcm.googleapis.com/fcm/send

Than change request type to POST. See below screenshot:

Now to click on Header and add two params Content-Type and Authorization.

Content-Type= application/json
Authorization=AIzaSyAEb3NhsfGw1ih5mn8cmrGUAXMp86waQ //FCM SERVER KEY

See below screenshot:

Now click on Body than select Row and add value as object like below

{ 
"to":"eB5papU2Xdc:APA91bFFvc3dXru1fN5JY8U19oHIpfGhPUx7Ll7v9vJYTsIGZ15mDwB2Wpep3flLK85IUqqs2WqJwjYHSDYX28oJ1wTP0R2TDc2ba_uVjUauDcp3pCNKr_0KlghOnS", 
 "notification" : {
 "body" : "New announcement assigned",
 "OrganizationId":"2",
 "content_available" : true,
 "priority" : "high",
 "subtitle":"Elementary School",
 "Title":"hello"
 },
 "data" : {
 "priority" : "high",
 "sound":"app_sound.wav",
 "content_available" : true,
 "bodyText" : "New Announcement assigned",
 "organization" :"Elementary school"
}
}

Now your Postman would look like this. Click Send button at top right.

Good luck!

Solution 4

For the new FCM HTTP v1 API, the method of testing push notifications through Postman has changed and the existing solutions only addressed the legacy method of testing push notifications: https://firebase.google.com/docs/cloud-messaging/send-message

To test on Postman with FCM HTTP v1 API, you will need to first fetch a short-lived Oauth 2 token. You can generate one as per the information on the Firebase site here: https://firebase.google.com/docs/cloud-messaging/auth-server

I generated mine using Python using the code below - remember to pip install the package so that you can import the package into your code successfully:

from oauth2client.service_account import ServiceAccountCredentials

def _get_access_token():
  """Retrieve a valid access token that can be used to authorize requests.

  :return: Access token.
  """
  credentials = ServiceAccountCredentials.from_json_keyfile_name(
      'service-account.json', FCM_SCOPE)
  access_token_info = credentials.get_access_token()
  return access_token_info.access_token

Once you have the token - you can insert it into your Postman under authorisation:

IMPORTANT:

In my case, I had struggled a bit to get this to work as I was trying to test a scheduled task that was going to send push notification every few minutes to FCM. I had printed the token to my logs and then taken that token to my Postman for testing, not realising that it already has been used in the scheduled calls to FCM.

In that case, because it has already been used, the token will no longer be valid and my Postman tests were all failing. In this case, you will need to generate fresh tokens for your Postman tests.

Solution 5

Look at below screenshot how Authorization key is set

Authorization : **key=**abcdefghijklmnopr2qrst253uv124wxyz_9shg

View more solutions

Comments

[Vinod Kumar Marupu]

{ "multicast_id": 4790719999662534961, "success": 0, "failure": 1, "canonical_ids": 0, "results": [ { "error": "InvalidRegistration" } ] } got this error

[Alireza Noorali]

This Article will be helpful to you: medium.com/android-school/…

[Ramis]

This answer can help: stackoverflow.com/a/62670409/1151916

[Ramesh-X]

You can find in this article, how to fcm send push notifications with postman via firebase messaging API

[Asymptote]

how to get to token? is there an API?

[praveen dewangan]

Read firebase android developer documentation

[phpdroid]

am getting sucess=1 but am not getting a notification on mobile

[praveen dewangan]

Hi phpdroid you need to check complete body, message is passing to your mobile but it is not able to pick the body

[DevOma]

how to send to all users, who installed app, instead of send to topic?

[CoolMind]

@phpdroid, see pluralsight.com/guides/…, freecodecamp.org/news/… and many others.

[phpdroid]

@CoolMind it's been 2 years thanks for suggestions tho!

[CoolMind]

Thanks, but currently it shows an error in HTML: "<TITLE>Invalid (legacy) Server-key delivered or Sender is not authorized to perform request.</TITLE>".

[CoolMind]

Thanks! At least, it shows a more suitable error, than "Invalid (legacy) Server-key...".

[CoolMind]

I think, you have right header, but maybe a configuration of Firebase project is not done. Have you added an Android or iOS application?

[CoolMind]

This works if you use a server key or legacy server key from Cloud Messaging settings (starting from "AAAA" or "Alza").

[CoolMind]

This works if you use a server key or legacy server key from Cloud Messaging settings (starting from "AAAA" or "Alza").

[CoolMind]

Also you should check google-services.json in your Android application. You need to download it from Firebase console and paste into Android application, then run on device.

[CoolMind]

I see, you already have --header "Authorization: key=<API_ACCESS_KEY> in curl and wrong header in Postman.

[CoolMind]

This answer is your question: stackoverflow.com/questions/56723045/….

[roghayeh hosseini]

@DevOma for send to all users, is needed to subscribe theme to 'all' topic. and so send to '/topics/all'

[Evgenii Vorobei]

where you got this Bearer token? If I take the server key, FCM throws 401

[Neo]

This sends to the given token only. How can I send it to all users from postman?

[Neo]

This method allows it to send to the specified token. How can we send to all the users?

[Shridhar]

I am getting this response but not the notification to the android app. Any idea?

[clauub]

This works like a charm and sends notifications instantly. A thing that should be changed is that Title to title !

[clauub]

What's the difference between notification and data object? Why do you use both?

[Ankit Mishra]

how we can convert same thing in nodejs using rest api

[Sharath B Naik]

This works for me. Thanks....

[Sergey Neskoromny]

This token is generated by the Firebase Admin SDK.