Firebase Realtime Database Management API

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

✓ Official Vendor SpecStorageDatabaseoauth27 EndpointsREST

For Agents

Provision, disable, re-enable, and delete Firebase Realtime Database instances so an agent can automate database environment setup across regions.

Quickstart

Get started with Firebase Realtime Database Management API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"provision a firebase realtime database instance"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Firebase Realtime Database Management API API.

Provision a Firebase Realtime Database instance in a chosen Google Cloud region

Disable a Realtime Database instance to stop reads and writes without deleting data

Re-enable a previously disabled Realtime Database instance

Soft-delete a Realtime Database instance and undelete it within the recovery window

GET STARTED

Start building with Firebase Realtime Database Management API API

Explore with Jentic

View OpenAPI Document

Use for: Provision a new Firebase Realtime Database instance in europe-west1, List all Realtime Database instances under a Firebase project, Find all disabled Realtime Database instances that should be cleaned up, Get the connection details for a specific Realtime Database instance

Not supported: Does not read or write data inside the database, manage security rules, or expose realtime listeners — use for Realtime Database instance lifecycle management only.

Use Cases

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

★ Per-Environment Realtime Database Provisioning

Stand up a fresh Realtime Database instance for each preview branch or staging environment using POST /v1beta/{+parent}/instances. Once provisioned, the instance has its own database URL that the application can target via Firebase SDKs, isolating test data from production. Provisioning is asynchronous and typically completes within seconds.

Call POST /v1beta/{+parent}/instances with parent=projects/PROJECT/locations/us-central1 and instanceId=staging-rtdb to create a new Realtime Database instance for the staging environment.

Cost Control via Disable and Re-enable

Temporarily disable a Realtime Database instance during long inactive periods to halt billable reads and writes without losing data. POST /v1beta/{+name}:disable suspends access while keeping the data intact, and POST /v1beta/{+name}:reenable restores access on demand. This is suited to seasonal apps and CI environments that idle outside business hours.

Call POST /v1beta/{+name}:disable on instance projects/PROJECT/locations/us-central1/instances/sandbox-rtdb to pause it overnight and POST /v1beta/{+name}:reenable to bring it back the next morning.

Soft-Delete Recovery Workflow

Recover from accidental deletion by undeleting a Realtime Database instance within the recovery window via POST /v1beta/{+name}:undelete. The instance must first be deleted using DELETE /v1beta/{+name}, after which it remains in a recoverable state. This avoids the need to restore from external backups for short-window mistakes.

Call POST /v1beta/{+name}:undelete on a recently deleted instance and confirm via GET /v1beta/{+name} that its state reads ACTIVE.

Agent-Managed Database Environments via Jentic

An AI agent using Jentic can manage the full lifecycle of Realtime Database instances on behalf of a developer team — provisioning new ones for branches, disabling idle ones, and undeleting accidentally removed ones. Jentic exposes all 7 management endpoints, the agent strings them together, and OAuth 2.0 credentials stay inside the Jentic vault.

Through Jentic, search for provision a firebase realtime database instance, load the instances.create operation, and execute it with parent=projects/my-project/locations/us-central1 and instanceId=preview-42-rtdb.

Key Endpoints

7 endpoints — the firebase realtime database management api enables programmatic provisioning and lifecycle management of realtime database instances inside a firebase project.

METHOD

PATH

DESCRIPTION

POST

/v1beta/{+parent}/instances

Create a new Realtime Database instance

GET

/v1beta/{+parent}/instances

List Realtime Database instances under a location

POST

/v1beta/{+name}:disable

Disable a Realtime Database instance

POST

/v1beta/{+name}:reenable

Re-enable a previously disabled instance

POST

/v1beta/{+name}:undelete

Undelete a previously deleted instance within the recovery window

DELETE

/v1beta/{+name}

Delete a Realtime Database instance

POST

/v1beta/{+parent}/instances

Create a new Realtime Database instance

GET

/v1beta/{+parent}/instances

List Realtime Database instances under a location

POST

/v1beta/{+name}:disable

Disable a Realtime Database instance

POST

/v1beta/{+name}:reenable

Re-enable a previously disabled instance

POST

/v1beta/{+name}:undelete

Undelete a previously deleted instance within the recovery window

Why though Jentic?

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

Credential isolation

Google OAuth 2.0 service-account credentials are stored encrypted in the Jentic vault. Agents receive a scoped access token at execution time and never see the underlying private key.

Intent-based discovery

Agents search Jentic with intents like provision a firebase realtime database instance and Jentic returns the instances.create operation along with its parent and instanceId parameters resolved from the spec.

Time to first call

Direct integration with the Realtime Database Management API: 1-2 days for OAuth, region selection, and lifecycle automation. Through Jentic: under 30 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Firebase Management API

Sets up the Firebase project that hosts Realtime Database instances.

Choose Firebase Management first to provision the project; use the Realtime Database Management API afterwards to add database instances.

Complementary

Firebase Rules API

Manages security rules controlling reads and writes inside Realtime Database instances.

Choose Firebase Rules to deploy the security rules document for an instance after provisioning it through the Realtime Database Management API.

Alternative

Firebase Storage API

Manages object-storage buckets rather than realtime database instances.

Choose Firebase Storage for binary blobs such as user uploads; use Realtime Database Management for low-latency JSON state synchronisation across clients.

FAQs

Specific to using Firebase Realtime Database Management API API through Jentic.

What authentication does the Firebase Realtime Database Management API use?

The API uses Google OAuth 2.0 with the firebase or cloud-platform scope. Through Jentic the OAuth credentials live in the encrypted Jentic vault and a scoped access token is supplied per request without exposing the service-account key.

Can I create a new Firebase Realtime Database instance with this API?

Yes. POST /v1beta/{+parent}/instances with parent=projects/PROJECT/locations/REGION and an instanceId creates a new Realtime Database instance. The response includes the instance name and database URL that client SDKs can connect to.

What are the rate limits for the Firebase Realtime Database Management API?

Google enforces standard googleapis.com per-project quotas for management endpoints, typically a few hundred requests per minute. Provisioning is also bounded by per-project instance quota, which can be raised via a Google Cloud quota increase request.

How do I disable a Realtime Database instance through Jentic?

Run pip install jentic, search for disable a firebase realtime database, load the instances.disable operation, and execute it with name=projects/PROJECT/locations/REGION/instances/INSTANCE. Sign up at https://app.jentic.com/sign-up.

Does the Firebase Realtime Database Management API let me read or write data inside the database?

No. This API only provisions and manages instance lifecycle. To read and write data inside a Realtime Database use the Firebase Realtime Database REST endpoints exposed at the instance's database URL, or the platform Firebase SDKs.

Is the Firebase Realtime Database Management API free?

The management API itself has no per-call charge under typical usage. The Realtime Database instances it provisions are billed by simultaneous connections, storage, and downloaded bandwidth at standard Firebase pricing.