Firebase Cloud Messaging Data API

Name: Firebase Cloud Messaging Data API API
Brand: Firebase Cloud Messaging Data API
Availability: InStock

✓ Official Vendor SpecAnalyticsProduct Analyticsoauth21 EndpointsREST

For Agents

Retrieve aggregated Firebase Cloud Messaging delivery data for Android apps so an agent can analyse push notification success and failure trends.

Quickstart

Get started with Firebase Cloud Messaging Data 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:
"retrieve firebase cloud messaging delivery data"

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

Capabilities

What an agent can do with Firebase Cloud Messaging Data API API.

Pull daily delivery counts for FCM push notifications grouped by analytics label

Diagnose Android push drop reasons such as quota exhaustion or device disconnection

Compare message acceptance versus dropped delivery volumes for an Android app

Surface FCM analytics labels that consistently underperform in delivery rate

GET STARTED

Start building with Firebase Cloud Messaging Data API API

Explore with Jentic

View OpenAPI Document

Use for: Retrieve Firebase Cloud Messaging delivery data for an Android app, Find all dropped FCM message reasons for the last 7 days, Get the daily push notification success rate for my Android app, List all analytics labels for which FCM deliveries failed

Not supported: Does not send push notifications, target individual devices, or expose per-message tracing — use for reading aggregated FCM delivery analytics on Android apps only.

Use Cases

Patterns agents use Firebase Cloud Messaging Data API API for, with concrete tasks.

★ Push Notification Delivery Health Monitoring

Track whether transactional and marketing push notifications sent through Firebase Cloud Messaging are reaching Android devices. The API returns daily counts of accepted, dropped, and delivered messages along with droppage reasons such as device disconnected or quota exceeded, letting product teams quantify notification reliability without building a custom telemetry pipeline. Integration takes under a day for a read-only dashboard.

Call the deliveryData.list endpoint for projects/123/androidApps/com.example.app and report the percentage of MESSAGE_OUTCOME_DROPPED events for the most recent 7 days.

A/B Test Notification Performance Comparison

Compare delivery and droppage metrics across Firebase Cloud Messaging analytics labels to identify which notification variants reach users most reliably. Each delivery record is grouped by analyticsLabel, so teams can break results down by experiment arm and aggregate by date. This is suited to weekly performance reports rather than per-message tracing.

List FCM delivery data filtered by analyticsLabel=promo_v2 and return total message_counts versus delivery_performance_percents for the trailing 14 days.

Push Drop Root Cause Investigation

When push notification volume looks healthy but engagement falls, the FCM Data API reveals whether messages are being dropped before delivery and why. The droppedReasonCounts breakdown returns counts by reason such as APP_FORCE_STOPPED, INVALID_REGISTRATION, or QUOTA_EXCEEDED so engineers can target fixes at the right layer.

Fetch delivery data for the last 28 days for a given Android app and produce a sorted breakdown of droppedReasonCounts so the top failure reason is clear.

Agent-Driven Notification Reliability Reports

An AI agent connected to Jentic can answer questions like why notification delivery dropped this week by querying the FCM Data API, parsing the delivery and droppage breakdowns, and surfacing actionable explanations alongside other Firebase signals. Through Jentic, the agent loads the deliveryData.list schema on demand and runs scoped OAuth requests without exposing the developer's Google credentials.

Through Jentic, search for retrieve firebase cloud messaging delivery data, load the deliveryData.list operation, and execute it for a target Android app with a date range covering the last 7 days.

Key Endpoints

1 endpoints — the firebase cloud messaging data api exposes aggregated delivery metrics for fcm push notifications sent to android applications.

METHOD

PATH

DESCRIPTION

GET

/v1beta1/{+parent}/deliveryData

List daily aggregated FCM message delivery data for an Android app

GET

/v1beta1/{+parent}/deliveryData

List daily aggregated FCM message delivery data for an Android app

Why though Jentic?

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

Credential isolation

Google OAuth 2.0 client secrets and refresh tokens are stored encrypted in the Jentic vault. Agents receive a scoped access token at execution time and never see the underlying Google service account credentials.

Intent-based discovery

Agents search Jentic with intents like retrieve firebase cloud messaging delivery data and Jentic returns the deliveryData.list operation with its parent path parameter and date filter schema.

Time to first call

Direct integration with FCM Data API: 1-2 days for OAuth, scope configuration, and pagination handling. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Firebase Cloud Messaging API

Sends the push notifications whose delivery metrics this API reports.

Choose FCM when the agent needs to actually send a push notification; use this Data API only to read aggregated delivery outcomes after sending.

Complementary

Firebase Management API

Manages the Firebase projects and Android apps referenced in delivery data queries.

Choose the Firebase Management API to discover androidApps resource names that are then used as the parent argument to deliveryData.list.

Alternative

Google Analytics Data API

Reports broader app and web analytics rather than push delivery telemetry.

Choose Analytics Data API when the agent needs general engagement metrics; use FCM Data API only when the question is specifically about push notification delivery success.

FAQs

Specific to using Firebase Cloud Messaging Data API API through Jentic.

What authentication does the Firebase Cloud Messaging Data API use?

The API uses Google OAuth 2.0 with the firebase.messaging or cloud-platform scope. Through Jentic the OAuth flow and refresh tokens are stored in the encrypted vault and never enter the agent's prompt context.

Can I retrieve per-message delivery status with the Firebase Cloud Messaging Data API?

No. The API only exposes daily aggregated counts via the deliveryData.list endpoint, grouped by date, analytics label, and droppage reason. For per-message tracing use FCM logging exports to BigQuery instead.

What are the rate limits for the Firebase Cloud Messaging Data API?

Google Cloud applies the standard per-project quota for googleapis.com endpoints, typically a few hundred read requests per minute per project, shared across the Firebase Management surface. Quotas can be reviewed and adjusted in the Google Cloud console under APIs and Services.

How do I list FCM delivery data for an Android app through Jentic?

Run pip install jentic, then through the Jentic SDK search for retrieve firebase cloud messaging delivery data, load the deliveryData.list operation, and execute it with parent set to projects/PROJECT_ID/androidApps/APP_ID. Sign up at https://app.jentic.com/sign-up.

Does the Firebase Cloud Messaging Data API cover iOS or web apps?

No. The deliveryData.list endpoint is currently only exposed under projects/{project}/androidApps. iOS APNs delivery analytics are not returned by this API.

Is the Firebase Cloud Messaging Data API free?

The API itself has no per-call charge under the Firebase free tier; standard Google Cloud project quotas apply. FCM message sending costs are unaffected by reading this delivery data.