Firebase Hosting API logo

Firebase Hosting API

Firebase Hosting API

Manage Firebase Hosting sites, preview channels, releases, versions, and file uploads from deployment pipelines.

Visit site ↗Health checked 9h ago
Use it when

Covers channels, releases, and versions end to end

Watch for

Focused on Hosting rather than Firestore or Functions

First check

Begin with an OAuth token that includes firebase or cloud-platform scope. List sites first, then test channels, versions:clone, and populateFiles before wiring the flow into your deployment pipeline.

Auth
oauth
CORS
No
HTTPS
Yes
Signup
Required
Latency
45 ms
Protocol
REST
Pricing

Uptime · 30-day window

Probes: 1Uptime: 100%Avg latency: 45ms
01

About this API

This API turns Firebase Hosting deployments into a scriptable surface, especially for teams that rely on preview channels, version cloning, and file population during CI/CD. The resource surface includes "/v1beta1/{name}", "/v1beta1/{parent}/channels", "/v1beta1/{parent}/domains", and "/v1beta1/{parent}/files", with groupings such as "projects" and "sites".

For backend teams, that is useful when the goal is to create preview channels for review environments, upload content files and publish a new release, or clone versions for rollback or reuse flows. The spec lists scopes such as "https://www.googleapis.com/auth/cloud-platform", "https://www.googleapis.com/auth/cloud-platform.read-only", and "https://www.googleapis.com/auth/firebase".

Focused on Hosting rather than Firestore or Functions The surface is still exposed under v1beta1

02

What you can build

  • 1Create preview channels for review environments
  • 2Upload content files and publish a new release
  • 3Clone versions for rollback or reuse flows
03

Strengths & limitations

Strengths

  • Covers channels, releases, and versions end to end
  • Supports both firebase and cloud-platform scopes
  • Fits naturally into CI build artifact flows

Limitations

  • Focused on Hosting rather than Firestore or Functions
  • The surface is still exposed under v1beta1
04

Example request

Generic template — replace <endpoint> with the real path from the docs.
curl https://google.com/<endpoint> \
  -H "Authorization: Bearer $ACCESS_TOKEN"
05

Getting started

Begin with an OAuth token that includes firebase or cloud-platform scope. List sites first, then test channels, versions:clone, and populateFiles before wiring the flow into your deployment pipeline.

06

Technical details

CORS: NoHTTPS: YesSignup: YesOpen source: No
Auth type
oauth
Pricing
unknown
Protocols
REST
Response time
45 ms
Last health check
5/12/2026, 7:37:31 AM
07

Tags

08

More from Google