Google Firebase Hosting API

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

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth217 EndpointsREST

For Agents

Programmatically deploy static sites to Firebase Hosting — create versions, upload files, manage preview channels, and roll out releases.

Install Jentic One Beta

Connect the Firebase Hosting API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Firebase Hosting 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 Hosting API.

Create and list Firebase Hosting sites under a project via /v1beta1/{parent}/sites

Create new versions and populate them with hashed file content via /v1beta1/{parent}:populateFiles

Roll out a version by creating a release on a site or preview channel

GET STARTED

Start building with Firebase Hosting API

Explore with Jentic

View OpenAPI Document

Use Cases

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

★ Custom CI/CD Deploys

Replace the firebase-tools CLI in CI with direct REST calls when you need fine-grained control. Create a version via POST /v1beta1/{parent}/versions, populate file hashes via /v1beta1/{parent}:populateFiles, upload missing files, finalize, then create a release. The flow integrates cleanly into bespoke pipelines and agent-driven deploys.

Create a new version for site 'my-app', populate files with the SHA256 manifest, upload missing files, finalize the version, and create a release on the live channel

Preview Channels for PR Reviews

Spin up isolated preview URLs per pull request via POST /v1beta1/{parent}/channels with a TTL. Each channel has its own release stream so reviewers see exactly the build under review without affecting production. Channels are auto-expired when their TTL elapses, removing manual cleanup.

POST /v1beta1/{parent}/channels with channelId='pr-482' and ttl='604800s', then create a release on that channel pointing to the PR build version

Safe Rollback via Version Clone

Use POST /v1beta1/{parent}/versions:clone to copy a known-good version into a new editable version, then create a release pointing to it. This avoids re-uploading files and gives rollback in seconds. Useful for incident response runbooks an agent can execute end-to-end.

POST /v1beta1/{parent}/versions:clone targeting the last known-good version, then create a release on the live channel using the cloned version

AI Agent Deploy Operations

Use Firebase Hosting through Jentic so a release agent can ship builds, open preview channels, and roll back without invoking firebase-tools. Jentic exposes the 17 REST endpoints as discoverable tools while keeping the OAuth2 access token in the vault, suitable for ChatOps deploy bots. Get started at https://app.jentic.com/sign-up

Through Jentic, search 'create a Firebase Hosting preview channel', load the /v1beta1/{parent}/channels schema, and execute with channelId='preview-feature-x' and ttl='86400s'

Key Endpoints

17 endpoints — the firebase hosting rest api enables programmatic management and deployment of firebase-hosted sites.

METHOD

PATH

DESCRIPTION

GET

/v1beta1/{parent}/sites

List sites under a project

POST

/v1beta1/{parent}/versions

Create a new version

POST

/v1beta1/{parent}:populateFiles

Populate file hashes for a version

POST

/v1beta1/{parent}/releases

Create a release on a channel

POST

/v1beta1/{parent}/channels

Create a preview channel

POST

/v1beta1/{parent}/versions:clone

Clone a version for rollback or branching

POST

/v1beta1/{parent}/domains

Add a custom domain to a site

GET

/v1beta1/{parent}/sites

List sites under a project

POST

/v1beta1/{parent}/versions

Create a new version

POST

/v1beta1/{parent}:populateFiles

Populate file hashes for a version

POST

/v1beta1/{parent}/releases

Create a release on a channel

POST

/v1beta1/{parent}/channels

Create a preview channel

Why Jentic?

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

Credential isolation

Google OAuth2 access tokens (or service-account credentials) are stored in the Jentic vault. The Authorization header is injected at execution time, so the deploy agent never holds a long-lived token in its context.

Intent-based discovery

Agents search by intent (e.g. 'create a Firebase Hosting release' or 'create a preview channel') and Jentic returns the matching operation with its parameters, removing the need to navigate 17 versioned endpoints.

Time to first call

Direct integration: 2-4 days to handle the version-populate-upload-finalize-release lifecycle. Through Jentic: under 1 hour for the API surface.

FAQs

Specific to using Firebase Hosting API through Jentic.

What authentication does the Firebase Hosting API use?

The API uses OAuth 2.0 (both implicit and authorization-code flows are supported in the spec). Most server agents use a service account with scopes that include `https://www.googleapis.com/auth/firebase`. Through Jentic, the access token is held in the vault and injected at execution time.

Can I create preview channels with the Firebase Hosting API?

Yes. POST /v1beta1/{parent}/channels creates a named channel with an optional TTL, and POST /v1beta1/{parent}/releases pins a version to that channel. Preview URLs are returned in the channel resource.

What are the rate limits for the Firebase Hosting API?

Firebase Hosting applies per-project quotas — typical defaults allow several deploys per minute per site. The API returns standard 429 responses; project-specific quotas are visible in the Google Cloud console under the firebasehosting.googleapis.com service.

How do I deploy a build through Jentic?

Search Jentic for 'create a Firebase Hosting version', load the /v1beta1/{parent}/versions schema, and execute against your site. Then call /v1beta1/{parent}:populateFiles, upload any missing files, finalize the version, and create a release on the live channel.

Can I rollback a Firebase Hosting deploy via the API?

Yes. Use POST /v1beta1/{parent}/versions:clone to clone a previous good version, then create a release on the live channel pointing to the cloned version. The rollback applies near-instantly.

Does the Firebase Hosting API support custom domains?

Yes. /v1beta1/{parent}/domains lists, creates, and updates custom domain mappings on a site. SSL certificates are provisioned automatically by Firebase.

Google Firebase Hosting API

Connect the Firebase Hosting API to your agent

Capabilities

Start building with Firebase Hosting API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs