Firebase Hosting API

Name: Firebase Hosting API API
Brand: Firebase Hosting API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureNetworkingoauth23 EndpointsREST

For Agents

Track and clean up long-running Firebase Hosting operations such as custom domain provisioning so an agent can manage Hosting deploys without manual console work.

Quickstart

Get started with Firebase Hosting 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:
"monitor firebase hosting operations"

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

Capabilities

What an agent can do with Firebase Hosting API API.

List long-running Firebase Hosting operations under a site or custom domain

Cancel an in-flight Firebase Hosting custom domain operation

Delete a completed Firebase Hosting operation resource

Monitor the state of asynchronous custom domain provisioning jobs

GET STARTED

Start building with Firebase Hosting API API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ Custom Domain Provisioning Monitoring

Provisioning a custom domain on Firebase Hosting kicks off a long-running operation. The Hosting v1 API lets pipelines list and inspect those operations under projects/{project}/sites/{site}/customDomains/{domain}/operations to confirm SSL issuance and DNS verification have completed before flipping traffic. Polling integration with a deploy pipeline takes a few hours.

Call GET /v1/{+name} on a Hosting custom-domain operation resource and check that done is true and error is unset before proceeding to flip DNS to the Hosting site.

Cancelling Stuck Custom Domain Setup

When a Firebase Hosting custom domain operation hangs because of DNS misconfiguration or repeated SSL issuance failures, the API supports cancelling the operation via POST /v1/{+name}:cancel. This frees up the underlying resource so engineers can retry the operation cleanly with the corrected DNS records.

Call POST /v1/{+name}:cancel on the in-flight custom domain operation and verify via GET /v1/{+name} that the operation now reports done with a cancellation status.

Operation History Cleanup

Old Firebase Hosting operation resources accumulate as deploys and domain changes happen over time. DELETE /v1/{+name} removes a completed operation record to keep the operations list focused on recent activity. This is a low-frequency hygiene task suited to weekly maintenance runs.

Call DELETE /v1/{+name} on an operation that has been done=true for over 30 days to prune the operation history under a customDomains resource.

Agent-Driven Hosting Pipeline Monitoring via Jentic

An AI agent connected through Jentic can watch Firebase Hosting deploys and custom domain operations on behalf of a release engineer, surfacing failures and cancelling stuck operations as needed. Jentic exposes the 3 Hosting v1 operation endpoints, the agent strings them together, and OAuth credentials stay sealed inside the Jentic vault.

Through Jentic, search for monitor firebase hosting operations, load the operations.list endpoint, and execute it for projects/PROJECT/sites/SITE/customDomains/DOMAIN to surface any operations whose done flag is still false after one hour.

Key Endpoints

3 endpoints — the firebase hosting rest api enables programmatic management of long-running operations behind firebase hosting sites and channels, including custom domain provisioning workflows.

METHOD

PATH

DESCRIPTION

GET

/v1/{+name}

List Firebase Hosting operations under a resource

POST

/v1/{+name}:cancel

Cancel a Firebase Hosting long-running operation

DELETE

/v1/{+name}

Delete a Firebase Hosting operation resource

GET

/v1/{+name}

List Firebase Hosting operations under a resource

POST

/v1/{+name}:cancel

Cancel a Firebase Hosting long-running operation

DELETE

/v1/{+name}

Delete a Firebase Hosting operation resource

Why though Jentic?

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

Credential isolation

Google OAuth 2.0 service-account credentials are stored in the Jentic vault. Agents receive a scoped access token per call, so the underlying private key never enters the agent's prompt or tool-call payloads.

Intent-based discovery

Agents search Jentic with intents like monitor firebase hosting operations and Jentic returns the operations.list, operations.cancel, and operations.delete endpoints with their resource-name parameters resolved from the spec.

Time to first call

Direct integration with the Hosting operations API: 1-2 days for OAuth and pipeline polling. 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 owns Hosting sites and custom domains.

Choose Firebase Management first to provision the project; use the Hosting API afterwards to monitor deploy and custom-domain operations.

Complementary

Google Cloud Run Admin API

Hosts dynamic backends that Firebase Hosting can route to with rewrites.

Choose Cloud Run for server-rendered or API backends; use Firebase Hosting alongside it to serve static assets and route specific paths to Cloud Run services.

Alternative

Google App Engine Admin API

Provides full app hosting rather than CDN-fronted static sites.

Choose App Engine when the workload needs full server hosting and language runtimes; use Firebase Hosting for static and JAMstack sites with optional Cloud Run rewrites.

FAQs

Specific to using Firebase Hosting API API through Jentic.

What authentication does the Firebase Hosting API use?

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

Can I deploy a new release with the v1 Firebase Hosting API endpoints exposed here?

No. The v1 endpoints in this spec cover long-running operation management only — list, cancel, and delete. Release deployment, version finalisation, and channel creation are handled in the broader Firebase Hosting REST surface and the firebase CLI; this spec is the operations-monitoring surface.

What are the rate limits for the Firebase Hosting API?

Google enforces standard googleapis.com per-project read and write quotas. Operation listing is a low-cost read endpoint, and pipelines that poll frequently should respect the per-minute project quota with backoff between polls.

How do I monitor a Firebase Hosting custom domain operation through Jentic?

Run pip install jentic, search for monitor firebase hosting operations, load the operations.list endpoint, and execute it for projects/PROJECT/sites/SITE/customDomains/DOMAIN/operations. Sign up at https://app.jentic.com/sign-up.

Does the Firebase Hosting API support cancelling stuck custom domain operations?

Yes. POST /v1/{+name}:cancel on the operation resource cancels the in-flight job. After cancellation the operation reports done=true with a cancellation status, allowing pipelines to retry custom domain setup with corrected DNS or verification records.

Is the Firebase Hosting API free?

Firebase Hosting is included with Firebase under standard free-tier limits. Bandwidth and storage above those limits are billed under the Hosting price list; the operations endpoints themselves do not incur additional charges.