Notice: This documentation is currently a work in progress for the upcoming v6 release and some content may be missing or incomplete. If you're not interested in testing out the alpha version of v6 then please click here to be taken to the v5 documentation.

edit  Edit page
message  Send Feedback

Getting started with Cloud Functions

Firebase Cloud Functions provides the ability to write and deploy HTTPS endpoints to a managed environment. This tutorial will cover setting up the Firebase CLI on your machine, writing a HTTPS function and querying the response in your React Native application.

To find out more about Cloud Functions, view Firebase's documentation.

This guide assumes you have a React Native & Firebase project setup and ready to use.

What are we building?

This tutorial will create a simple endpoint which returns a list of products using the Faker library. This data will be used to create a simple product listing screen on your React Native application.

Installing the Firebase CLI

Firebase provides a CLI which is required to build and deploy Cloud Functions. To install the CLI, install the firebase-tools package globally on your computer from your terminal:

npm install -g firebase-tools

Once installed, login to Firebase with the CLI. This process will automatically open a browser instance giving you the ability to login to your Firebase account.

firebase login

Once logged in, create a new directory on your computer called product-api. This will be used as our working directory where our Cloud Functions will be written and deployed from. Within this directory, run the following command from your terminal to initialize a new project structure:

firebase init functions

You will be offered two options for language support, for this tutorial select JavaScript. Allow the CLI to install dependencies using npm. Once complete your project structure will look like this:

+- .firebaserc # Hidden file that helps you quickly switch between
| # projects with `firebase use`
+- firebase.json # Describes properties for your project
+- functions/ # Directory containing all your functions code
+- .eslintrc.json # Optional file containing rules for JavaScript linting.
+- package.json # npm package file describing your Cloud Functions code
+- index.js # main source file for your Cloud Functions code
+- node_modules/ # directory where your dependencies (declared in
# package.json) are installed

Writing your first Cloud Function

The Firebase CLI has created a project structure and also installed a number of dependencies which will be used to build our Cloud Functions.

Before getting started, install the faker library in the functions directory using npm:

cd functions/
npm install --save faker

Now it's time to write your first Cloud Function! Open up the generated functions/index.js file in your chosen editor. The CLI has already imported the firebase-functions package required to build a Cloud Function. Firebase used named exports to help identify functions. These exports are used to build the API endpoint name which will be accessible from our React Native application.

For this tutorial, we are creating a product listing API. Go ahead and create a new HTTPS callable named function called products:

// functions/index.js
const functions = require('firebase-functions');
exports.products = functions.https.onRequest((request, response) => {

The onRequest callback returns two objects:

  • request: contains information about our incoming request, such as headers and parameters.
  • response: provides a number of functions to help return data in a standardized format back to users.

For in-depth information on these objects, please reference the express documentation.

We can now return an array of our products, generated from the faker library. As we are mocking a dataset, it's important to keep consistent results for each request. The data should be generated before the request is received, rather than a new dataset being generated on each request:

// functions/index.js
const functions = require('firebase-functions');
const faker = require('faker');
// Initialize products array
const products = [];
// Max number of products
const LIMIT = 100;
// Push a new product to the array
for (let i = 0; i < LIMIT; i++) {
name: faker.commerce.productName(),
price: faker.commerce.price(),
exports.products = functions.https.onRequest((request, response) => {
return response.json(products);

Testing your functions

Before deploying our functions project, we can run the serve command which builds a locally accessible instance of our Cloud Functions. Run the following command from within the functions/ directory:

npm run serve

Once booted, the CLI will be provide a local web server with the products endpoint openly available, e.g:

functions: products: http://localhost:5000/rnfirebase-demo/us-central1/products

In your terminal (or browser), access the endpoint provided. Our list of generated products is ready for use.

curl -i -H "Accept: application/json" -H "Content-Type: application/json" -X GET http://localhost:5000/rnfirebase-demo/us-central1/products

Note: we use response.json() to automatically apply headers so our request can expect a valid JSON Content-Type response.

Handling pagination

Our HTTPS endpoint currently returns all 100 results. Whilst this is ok for demo purposes, in a real life application it's important to think about the user. More data requires more bandwidth and longer response times (especially when used with a real database!). Paginating the data allows us to only return a subset of the entire dataset, and is achievable with our own Cloud Function using request parameters.

Lets setup the API to accept page & limit parameters, which will be used to limit and skip our dataset:

exports.products = functions.https.onRequest((request, response) => {
const { page = 1, limit = 10 } = request.query;
return response.json(products);

We access the params from the query field on the request object. It's also important to ensure default values are set in-case the incoming request mitigates them. Using our query parameters we can now paginate the data:

exports.products = functions.https.onRequest((request, response) => {
const { page = 1, limit = 10 } = request.query;
const startAt = (page - 1) * limit;
const endAt = startAt + limit;
return response.json(products.slice(startAt, endAt));

When requesting our data, you will be limited to the first 10 results! To change the pagination values, change the query parameters on the request, e.g:

curl -i -H "Accept: application/json" -H "Content-Type: application/json" -X GET http://localhost:5000/rnfirebase-demo/us-central1/products?page=2&limit=15

Integrating with React Native

With the HTTPS endpoint now ready for use, lets go ahead and integrate our dataset into a React Native application using the Cloud Functions module. We'll use the [/v6/functions](Cloud Functions) package to call our endpoint directly, and display the product listing using a ListView.

If you haven't already, install the @react-native-firebase/functions package by following the instructions on the [/v6/functions](Cloud Functions) page.

Firstly, we need to change our endpoint function. We have currenntly been using the onRequest method which exposes a HTTPS endpoint, however we want to now expose a named endpoint which our React Native app can call with the httpsCallable method.

exports.products = functions.https.onCall((input, context) => {
const { page = 1, limit = 10 } = input;
const startAt = (page - 1) * limit;
const endAt = startAt + limit;
return products.slice(startAt, endAt);

What has changed?

  • onRequest -> onCall: We've now created a named function called products.
  • (request, response) -> (input, context): The input argument contains parameters from our httpsCallable method call, and the context contains information relating to the request.
  • request.query -> input: Any parameters are extracted from the input argument.
  • return response.json -> return: Any data returned is sent back directly to the function.

All httpsCallable calls require authentication, to ensure only your own app is making calls to the endpoint. For ease, we'll create an annoymous user in our app before making the request.

The @react-native-firebase/auth package is required to make calls with httpsCallable. Ensure it is installed and that anonymous sign-in is enabled on the Firebase Console for your project.

With your React Native app ready to go, edit the entry point component to import our React Native Firebase modules. We also need to point our app at the local functions endpoint:

import React, { useState, useEffect } from 'react';
import firebase from '@react-native-firebase/app';
import '@react-native-firebase/functions';
import '@react-native-firebase/auth';

We'll now build out our component, first authenticating the user and making a request to our named function using the httpsCallable methood:

function App() {
const [loading, setLoading] = useState(true);
const [products, setProducts] = useState([]);
// Sign in, and load the products
async function loadProducts() {
try {
// Create or sign the user into a anonymous account
await firebase.auth().signInAnonymously();
// call our named products endpoint
const { data } = await firebase.functions().httpsCallable('products')({
page: 1,
limit: 15,
// Update component state
} catch (e) {
useEffect(() => {
}, []);
return null;

Great, we're now able to grab our products directly from the function with an added layer of security with no extra work!

Lets go ahead and handle our components state, rendering the products once they've been downloaded:

import { FlatList } from 'react-native';
// ...
function App() {
// ...
if (loading) {
// Show a loading spinner or text here
return null;
return (
data={, i) => {
return {
key: `${}-${i}`, // Provide a unique key for FlatList
renderItem={({item}) => (
<Text>{} (${item.price})</Text>


By providing the FlatList with our product data set and returning a simple text based row for each product, the output is a scrollable list of our products and their prices. It's now straightforward to add more data to your products and build out an awesome user interface - give it a go!

Deploying your Cloud Functions to production

With our app successfully integrating with our HTTPS callable Cloud Function, we can deploy our project to a production ready instance on Firebase. Back in our product-api project, run the following command from your terminal, inside of the functions/ directory:

npm run deploy

Once complete, your Cloud Function will also be available from a publicly accessible endpoint if required, for example:

Updating the functions emulator

With our Cloud Functions deployed, we are now able to update the application to only use the development endpoint whilst developing. Common practice is to use the React Native __DEV__ with a conditional:

import functions from '@react-native-firebase/functions';
if (__DEV__) {
// Use a local emulator in development


This tutorial has only scratched the surface of what is achievable with Cloud Functions and React Native. Our product api example whilst simple provides a good example on developing an API using Cloud Functions.

If you're interested in learning more, check out the following resources: