Google Firebase Management API

Name: Firebase Management API
Brand: Firebase Management API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsProject Managementoauth221 EndpointsREST

For Agents

Programmatically create Firebase projects, register iOS, Android, and Web apps, and retrieve SDK configuration so an agent can bootstrap Firebase environments end to end.

Install Jentic One Beta

Connect the Firebase Management API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Firebase Management API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Firebase Management API.

Add Firebase to an existing Google Cloud project to enable Firebase services

Retrieve runtime SDK configuration for an Android, iOS, or Web app

GET STARTED

Start building with Firebase Management API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Firebase Management API for, with concrete tasks.

★ Automated Firebase Project Bootstrapping

Provision a new Firebase project, finalise its location, and register the iOS, Android, and Web apps a team needs in a single automation run. The Management API turns a process that normally involves several Firebase console screens into a deterministic script suitable for environment-per-branch workflows. Bootstrapping an end-to-end staging environment takes minutes once the script is in place.

Call POST /v1beta1/{+project}:addFirebase to enable Firebase on a Cloud project, then POST /v1beta1/{+parent}/androidApps with packageName=com.example.app and POST /v1beta1/{+parent}/iosApps with bundleId=com.example.app to register both clients.

SDK Config Retrieval for CI/CD

Fetch the up-to-date SDK configuration for Firebase Android, iOS, and Web apps so build pipelines can inject google-services.json, GoogleService-Info.plist, and Web init configs at build time rather than committing them to source control. The webApps.getConfig endpoint returns the JSON config while androidApps and iosApps expose equivalent platform-specific configs.

Call GET /v1beta1/{+name}/config on the resource projects/PROJECT/webApps/APPID and write the returned JSON to the build artifact directory.

Android Fingerprint Management for App Auth

Manage Android SHA-1 and SHA-256 certificate fingerprints needed by Firebase Authentication, Dynamic Links, and App Check via the projects.androidApps.sha endpoints. The API supports listing existing fingerprints, adding fingerprints from new signing keys, and removing rotated ones. This avoids ad-hoc updates in the Firebase console when signing keys change.

Use POST /v1beta1/{+parent}/sha to register a new SHA-256 fingerprint on the Android app projects/PROJECT/androidApps/APPID and confirm via GET /v1beta1/{+parent}/sha that it is listed.

Agent-Driven Firebase Environment Provisioning

An AI agent connected through Jentic can stand up a complete Firebase environment in response to a single intent like create a new staging Firebase project for the launch app. Jentic loads the relevant Firebase Management endpoints, the agent strings together project enablement, app registration, and config retrieval, and the OAuth 2.0 flow is handled transparently.

Through Jentic, search for register a firebase android app, load the androidApps.create operation, and execute it with parent=projects/my-project and packageName=com.example.staging.

Key Endpoints

21 endpoints — the firebase management api enables programmatic setup and lifecycle management of firebase projects and the ios, android, and web apps registered inside them.

METHOD

PATH

DESCRIPTION

GET

/v1beta1/projects

List Firebase projects

POST

/v1beta1/{+name}:remove

Remove a Firebase app from a project

POST

/v1beta1/{+name}:undelete

Undelete a previously removed Firebase app

GET

/v1beta1/{+parent}/androidApps

List Android apps under a Firebase project

POST

/v1beta1/{+parent}/androidApps

GET

/v1beta1/availableProjects

List Cloud projects eligible to add Firebase

GET

/v1beta1/projects

List Firebase projects

POST

/v1beta1/{+name}:remove

Remove a Firebase app from a project

POST

/v1beta1/{+name}:undelete

Undelete a previously removed Firebase app

GET

/v1beta1/{+parent}/androidApps

List Android apps under a Firebase project

POST

/v1beta1/{+parent}/androidApps

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google OAuth 2.0 service-account keys for the Firebase Management API are stored in the Jentic vault. Agents receive scoped access tokens with the cloud-platform or firebase scope at call time and never see the raw private key.

Intent-based discovery

Agents search Jentic with intents like create a firebase project or register a firebase android app and Jentic returns the matching addFirebase, androidApps.create, and iosApps.create operations with their input schemas.

Time to first call

Direct integration with Firebase Management API: 2-4 days for OAuth, project setup automation, and long-running-operation handling. Through Jentic: under 1 hour.

FAQs

Specific to using Firebase Management API through Jentic.

What authentication does the Firebase Management API use?

The API uses Google OAuth 2.0 with the firebase or cloud-platform scope. Through Jentic, OAuth credentials are stored in the encrypted vault and a scoped access token is supplied at execution time without exposing the underlying client secret.

Can I add Firebase to an existing Google Cloud project with the Firebase Management API?

Yes. POST /v1beta1/{+project}:addFirebase enables Firebase on a Cloud project that you already own. After the long-running operation completes, the project is visible in the Firebase console and accepts further app registration calls.

What are the rate limits for the Firebase Management API?

Google enforces the standard googleapis.com per-project quota, typically a few hundred requests per minute for management-style endpoints. Bulk app registration scripts should add backoff and respect the long-running-operation lifecycle returned by addFirebase and similar calls.

How do I register an Android app in a Firebase project through Jentic?

Run pip install jentic, search for register a firebase android app, load the androidApps.create operation, and execute it with parent=projects/PROJECT and packageName=com.example.app. Sign up at https://app.jentic.com/sign-up.

Does the Firebase Management API return google-services.json or GoogleService-Info.plist?

Yes. The androidApps and iosApps resources expose getConfig endpoints that return the JSON or plist content as a base64 payload, suitable for writing into a CI build artifact for Android and iOS clients.

Is the Firebase Management API free?

The Management API is included with Firebase at no extra charge; you pay only for the Firebase services your provisioned apps consume, such as Firestore, Authentication, or Cloud Messaging beyond their free quotas.

Google Firebase Management API

Connect the Firebase Management API to your agent

Capabilities

Start building with Firebase Management API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs