Firebase Cloud Messaging API

  • Updated on Oct 9, 2025
  • Published on Mar 26, 2024
  • 3 minute(s) read
Prev Next

Suggested reading: New FCM Quota System and Its Impact on Message Delivery

If this is your first time integration to Insider, get started with Android Integration, Firebase Messaging Service, and Firebase Cloud Messaging pages.

To integrate Firebase Cloud Messaging API, you should:

1. Get Firebase Cloud Messaging API Key
2. Control on Firebase Console
3. Create Service Account
4. Generate JSON Credentials
5. Upload JSON Credentials to Insider

Get Firebase Cloud Messaging API Key

1. Navigate to Inone > Settings > Mobile App Settings > Push Certificates.

Firebase cloud messaging credentials

2. Go to the Android Certificate section where you can see your current credentials. Save the Firebase Cloud Messaging API Key to use it later.

Control On Firebase Console

1. Go to Firebase Console to navigate to Project Overview > Project Settings > Cloud Messaging.

2. Go to the Cloud Messaging API (Legacy) section. Make sure that the used Server Key on Insider matches the one you have in your Firebase project.
Server key

Your title goes here
Ensure that Firebase Cloud Messaging API product is enabled on the related app's Google Cloud Console. You can check through the link here.

Create Service Account

You will need a new service account so that Insider does not have any issue when registering FCM tokens.

1. Go to Google Cloud > Service Accounts, and choose your project to click the +Create Service Account button.
Create service account

2. Fill in the required fields in Service account details, and click the Create and Continue button to save your changes.
Service account details

3. In Grant this service account access to project section, choose Firebase Cloud Messaging API Admin from the Select a role list, and click the Done button. 

If you need different types of roles, you can create custom roles.

Your title goes here
❗Make sure to select the Firebase Cloud Messaging API Admin role, but not the Firebase Cloud Messaging Admin role.

Generate JSON Credentials

You should generate JSON credentials through FCM service accounts to upload to Insider later. You can generate your credentials using two methods: Google Cloud Console or Firebase Console.

Google Cloud Console

1. Go to Google Cloud IAM & Admin > Service accounts, and select your project.

2. Find the FCM service account you created earlier, and click the menu against your account to go to Manage keys.
Manage keys

3. Click the Add Key > Create New Key button.

4. Choose JSON on the pop-up, and click the Create button.
Create private key

Your title goes here
As Google also stated, make sure to store the downloaded file securely, as the private key cannot be recovered if lost. You should store it in a secure place on your computer, as it should not be compromised. You can delete it after you upload it to Insider.

Firebase Console

You should generate JSON credentials through FCM service accounts to upload to Insider later.

1. Go to Firebase Console to navigate to Project Overview > Project Settings > Service Accounts.

2. Make sure the "node.js" option is selected and click the Generate New Private Key button to download the needed JSON credentials.


Your title goes here
As Google also stated, make sure to store the downloaded file securely, as the private key cannot be recovered if lost. You should store it in a secure place on your computer, as it should not be compromised. You can delete it after you upload it to Insider.

Upload JSON Credentials to Insider

1. Navigate to Inone > Settings > Mobile App Settings > Push Notification.

2. Go to the Android Certificate section, choose Firebase Cloud Messaging Credentials option, and click the Add Credentials button.

3. Once the upload is completed, this means that you have saved it to the Insider panel.

Now your messages will be completed through the new Firebase.

Caution List

  • Remember that your credentials and JSON file should match your project correctly. You can re-check it and re-upload it any time.
  • Keep in mind that you can switch to the legacy system anytime you face issues with your JSON credentials or file until Google deprecates the Legacy API.
  • Remember that Google deprecated and sunsetted the Legacy API in June 2024. That's why we recommend starting to use the new API after uploading the correct JSON credentials. 
  • As Google will wipe out legacy endpoints, Insider will not support the Legacy system anymore either. Your selection will be automatically converted to the new API even if you do not select it by then.
  • After uploading and saving the JSON file to Insider, you do not need to keep it in your downloaded folder. You can delete it once the upload is completed.
Related articles