Google Firebase App Distribution API
Browse all Google APIs40
AI ReadinessNon-Ready (F)40/100
Official vendor OpenAPI document · agent-readyDeveloper ToolsCi Cdoauth218 EndpointsREST
For Agents
Upload Android and iOS pre-release builds to Firebase App Distribution and distribute them to tester groups so an agent can ship beta builds straight from CI.
Use for: Upload an Android APK to Firebase App Distribution, Distribute the latest iOS build to the QA tester group, Find all testers in the beta group for an Android app, Add a list of email addresses to a tester group
Not supported: Does not publish to the App Store or Google Play production tracks, run automated UI tests, or collect crash analytics - use for pre-release iOS and Android binary distribution to testers only.
The Firebase App Distribution API automates pre-release distribution of iOS and Android binaries to internal testers, QA teams, and beta groups. It exposes operations to upload release binaries, distribute releases to tester groups, manage testers and groups, and track upload long-running operations. Use it to wire up CI pipelines so each merge produces a build automatically delivered to the right tester group without manual TestFlight or Play Console steps.
Install Jentic One Beta
Connect the Firebase App Distribution API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Firebase App Distribution 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Ffirebaseappdistribution" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fgoogleapis.com%2Ffirebaseappdistribution" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 App Distribution API.
Upload an Android APK or iOS IPA as a Firebase App Distribution release
Distribute a specific release to one or more tester groups or individual emails
Add and remove testers in batch from a Firebase App Distribution group
Wait for a release upload long-running operation to complete before notifying testers
Manage tester groups for a Firebase App Distribution app
Use Cases
Patterns agents use Firebase App Distribution API for, with concrete tasks.
★ CI-Driven Beta Build Distribution
Wire a CI pipeline to upload every passing main-branch build to Firebase App Distribution, wait for the upload operation to complete, and distribute the release to a named tester group. The API replaces manual TestFlight or Play internal-track uploads with a deterministic POST /v1/{+app}/releases:upload call followed by POST /v1/{+name}:distribute. Pipeline integration takes a few hours.
Call POST /v1/{+app}/releases:upload with the APK binary, poll the returned operation via GET /v1/{+name}/operations until done, then POST /v1/{+name}:distribute with groupAliases=[qa-team].
Tester Group Lifecycle Management
Keep tester groups in sync with HR systems by batch-adding new joiners and removing leavers via the App Distribution API. POST /v1/{+group}:batchJoin adds testers and POST /v1/{+group}:batchLeave removes them, while DELETE and PATCH on the group resource support full lifecycle changes. This is suited to teams running large internal beta programmes.
Call POST /v1/{+group}:batchJoin on the group projects/PROJECT/groups/qa-team with emails for the latest joiners list and confirm via GET /v1/{+name} that the group size has increased accordingly.
Release Cancellation and Operation Monitoring
When a build is uploaded but discovered to be defective before distribution, the App Distribution API supports cancelling the in-flight long-running operation via POST /v1/{+name}:cancel and listing recent operations via GET /v1/{+name}/operations. This avoids shipping a broken binary to testers and gives platform teams a record of upload activity.
Call POST /v1/{+name}:cancel on the in-flight upload operation for an Android app and verify by GET /v1/{+name}/operations that its state has moved to CANCELLED.
Agent-Driven Beta Releases via Jentic
An AI agent connected through Jentic can ship a beta build in response to a one-line release request from a developer. Jentic exposes the 18 App Distribution endpoints, the agent loads upload, distribute, and operation polling calls, and OAuth 2.0 credentials remain in your Jentic One instance. The agent can also notify the right tester group based on the release notes.
Through Jentic, search for distribute a release to firebase testers, load the releases.distribute operation, and execute it with name=projects/PROJECT/apps/APP/releases/REL and groupAliases=[beta].
Key Endpoints
18 endpoints — the firebase app distribution api automates pre-release distribution of ios and android binaries to internal testers, qa teams, and beta groups.
METHOD
PATH
DESCRIPTION
POST
/v1/{+app}/releases:upload
Upload an APK or IPA as a Firebase App Distribution release
POST
/v1/{+name}:distribute
Distribute a release to tester groups
POST
/v1/{+group}:batchJoin
Batch-add testers to a group
POST
/v1/{+group}:batchLeave
Batch-remove testers from a group
POST
/v1/{+name}:wait
Wait for a long-running operation to complete
POST
/v1/{+name}:cancel
Cancel a long-running operation
POST
/v1/{+app}/releases:upload
Upload an APK or IPA as a Firebase App Distribution release
POST
/v1/{+name}:distribute
Distribute a release to tester groups
POST
/v1/{+group}:batchJoin
Batch-add testers to a group
POST
/v1/{+group}:batchLeave
Batch-remove testers from a group
POST
/v1/{+name}:wait
Wait for a long-running operation to complete
POST
/v1/{+name}:cancel
Cancel a long-running operation
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
F
Firebase App Distribution API
- Non-Ready (F)40/100
49
Foundational Compliance56
Developer Experience & Jentic Compatibility18
AI-Readiness & Agent Experience94
Agent Usability63
Security60
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
49
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: D+Signals: 4
73%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
25%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
18
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
73%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
60
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C+Signals: 1
60%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Firebase App Distribution API by hand means setting up Google OAuth 2.0 with a service account, requesting the cloud-platform scope, and handling the upload plus long-running distribute operations yourself. Through Jentic you install once, import the Firebase App Distribution API from the API Directory, store the service-account credential once, and your agent calls it.
Permission scoping
App Distribution puts the app and tester group in the URL path (/v1/{app}/releases:upload, /v1/{group}:batchJoin), so a rule can pin your agent to one app or tester group and nothing else. You choose the operations it may call, so ones like batchLeave are not included unless you add them.
Credential isolation
Your Google service-account credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'distribute a release to Firebase testers' or 'upload a build', and Jentic returns the matching Firebase App Distribution operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Firebase App Distribution API through Jentic.
What authentication does the Firebase App Distribution API use?
The API uses Google OAuth 2.0 with the cloud-platform or firebase scope, typically from a service account configured in CI. Through Jentic, OAuth credentials are stored encrypted in the vault and a scoped access token is supplied per request without exposing the service-account key.
Can I distribute a release to a specific tester group with the Firebase App Distribution API?
Yes. POST /v1/{+name}:distribute on a release resource accepts groupAliases and testerEmails arrays so you can target named groups, individual testers, or both at once. Testers receive an email with install instructions for the new build.
What are the rate limits for the Firebase App Distribution API?
Google applies the standard googleapis.com per-project quota for management endpoints. Release uploads return long-running operations and should be polled with exponential backoff rather than tight loops; very large APK and IPA payloads may take several minutes to process.
How do I upload a beta APK through Jentic?
Run pip install jentic, search for upload an apk to firebase app distribution, load the releases.upload operation, and execute it with the binary payload and the parent app resource name. Get started with Jentic One, the self-hosted execution layer.
Does the Firebase App Distribution API support cancelling an in-flight upload?
Yes. POST /v1/{+name}:cancel on the long-running operation returned by an upload or distribute call moves the operation to a CANCELLED state, allowing pipelines to abort distribution of a build that fails post-upload smoke tests.
Is the Firebase App Distribution API free?
Firebase App Distribution is included with Firebase at no extra charge for typical pre-release usage. Standard Firebase project quotas apply, and binary storage falls under the Firebase project's storage usage.
Can I limit what my agent is allowed to do with the Firebase App Distribution API?
Yes. Jentic One runs self-hosted, so your own rules decide which Firebase App Distribution operations and credentials the agent may use. Because the app and tester group sit in the URL path (/v1/{app}/releases:upload, /v1/{group}:batchJoin), you can pin the agent to a single app or a single tester group and nothing else. You also choose the exact operations it may call, so destructive ones like batchLeave stay unavailable unless you add them.
GET STARTED