Watch demos on how to build & run AI-powered apps with Firebase at Demo Day '24. Watch now.

Firebase Remote Config API

The Firebase Remote Config API lets developers change the behavior and appearance of their apps without requiring users to download an app update. It is an alternative to, but can be used in tandem with, the Firebase console at https://console.firebase.google.com.

Service: firebaseremoteconfig.googleapis.com

To call this service, we recommend that you use the Google-provided client libraries. If your application needs to use your own libraries to call this service, use the following information when you make the API requests.

Discovery document

A Discovery Document is a machine-readable specification for describing and consuming REST APIs. It is used to build client libraries, IDE plugins, and other tools that interact with Google APIs. One service may provide multiple discovery documents. This service provides the following discovery document:

https://firebaseremoteconfig.googleapis.com/$discovery/rest?version=v1

Service endpoint

A service endpoint is a base URL that specifies the network address of an API service. One service might have multiple service endpoints. This service has the following service endpoint and all URIs below are relative to this service endpoint:

https://firebaseremoteconfig.googleapis.com

REST Resource: v1.projects

Methods
`getRemoteConfig`	`GET /v1/{project=projects/*}/remoteConfig` Get a project's Remote Config template and associated ETag header.
`updateRemoteConfig`	`PUT /v1/{project=projects/*}/remoteConfig` Publish a project's Remote Config template.

REST Resource: v1.projects.remoteConfig

Methods
`downloadDefaults`	`GET /v1/{project=projects/*}/remoteConfig:downloadDefaults` Get a project's current Remote Config template parameters and default values in JSON, property list (plist), or XML format.
`listVersions`	`GET /v1/{project=projects/*}/remoteConfig:listVersions` Get a list of `Remote Config template versions` that have been published, sorted in reverse chronological order.
`rollback`	`POST /v1/{project=projects/*}/remoteConfig:rollback` Roll back a project's published Remote Config template to the one specified by the provided version number.