# Firebase Cloud Messaging (FCM)

Medable Cortex supports Firebase Cloud Messaging (FCM), which inherits the reliable and scalable GCM infrastructure. As of April 10, 2018, Google has deprecated GCM. The GCM server and client APIs are deprecated and will be removed as soon as April 11, 2019. Medable will enable the following features to allow you to migrate to FCM.

![Adding the Firebase FCM Server Key Field to the existing Admin UI](https://files.readme.io/18fd557-image2019-3-15_18-4-6.png)

Adding the Firebase FCM Server Key Field to the existing Admin UI![Adding the Firebase FCM Server Key Field to the existing Admin UI](https://files.readme.io/b799bf3-image2019-3-15_18-4-59.png)

Adding the Firebase FCM Server Key Field to the existing Admin UI

You can lookup the FCM token with the following call.Text

```
[{'firebase.token': 1}, {unique: true, partialFilterExpression: { 'firebase.token': { $exists: true } }, name: 'idxFCMToken'}
```

You can call route to allow refreshing of firebase token (the CURRENT location will be updated)Text

```
POST /locations/FCMToken/
{"token": "..."}
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.medable.com/cortex-api/scripting/notifications/firebase-cloud-messaging.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.