Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases
Devices
Build
Test
Publish
Connect
Documentation
Skip to main content
You can use the Vitals API to programmatically access app health metrics, such as crash rate, app not responding (ANR) rate, and low memory killer (LMK) rate, for your Fire TV and Fire tablet apps. These metrics are organized into metric sets, which are logical groupings of related metrics that share common attributes (freshness and granularity) and can be queried together. Each metric set supports dimensions that you can use to filter results or produce breakdowns. Use of the Vitals API is subject to the Program Materials License Agreement.

Prerequisites

You need the following before you can call the API:
  • An Amazon Developer Account with Admin level credentials
  • A Security Profile mapped to the Reporting API (created through the Developer Console > My Settings > API Access)
  • The Client ID and Client Secret from the profile’s Web Settings tab
  • Your app’s package name

How it works

Data flows from raw crash logs and performance telemetry on devices into daily and hourly aggregation tables.
  • Daily metrics provide one data point per day, available at T-1 day.
  • Hourly metrics provide one data point per hour, available at T-2 hours. This is useful for early regression detection after a release.
Explore the API using the interactive sandbox in the Developer Console. For more details, see API Explorer.

Freshness

Each metric set offers a standard GET method to retrieve the timestamp of the latest available data, known as freshness. Since a metric set can support multiple granularities (daily, hourly), the operation returns one freshness value per supported granularity. You should always check freshness before querying to know what date range will return data.

Data queries

To access the data in a metric set, use the POST :query method. Each query must specify a granularity and a time range. Together with the metrics you want to access, you can specify dimensions to break down the aggregations or specify filters to narrow results without adding breakdowns. The results differ depending on whether you do or don’t specify dimensions with your query.
  • With dimensions: You get one row per unique dimension combination per time period.
  • Without dimensions: You get a single aggregate number per time period

Available metric sets

The table below lists all available metric sets and their supported metrics.
Metric SetDescriptionSupported Metrics
crashMetricSetCrash rate and event countscrashRate (Decimal): % of distinct users with at least one crash.
crashRate7dUserWeighted (Decimal): 7-day user-weighted rolling average.
crashRate28dUserWeighted (Decimal): 28-day user-weighted rolling average.
userPerceivedCrashRate (Decimal): % of users with crash during foreground use.
userPerceivedCrashRate7dUserWeighted (Decimal): 7-day rolling average of foreground crash rate.
userPerceivedCrashRate28dUserWeighted (Decimal): 28-day rolling average of foreground crash rate.
distinctDevices (Integer): Approximate active device count.
crashCount (Integer): Total crash event occurrences.
anrMetricSetANR rate and event countsSame structure as crash metrics, with anrRate and userPerceivedAnrRate variants, plus distinctDevices and anrCount (Integer): Total ANR event occurrences.
lmkMetricSetLMK rate and event countsSame structure as crash metrics, with lmkRate and userPerceivedLmkRate variants, plus distinctDevices and lmkCount (Integer): Total LMK event occurrences.
issuesMetricSetTop crash/ANR issues by frequencyerrorEventCount (Integer): Total error events for a crash signature.
affectedDeviceCount (Integer): Distinct devices affected.
reportText (String): Crash stacktrace or ANR trace.

Dimensions

Each metric set supports a common set of dimensions for filtering and breakdowns. Unless otherwise specified, all metrics can be broken down or filtered by all available dimensions.
Last modified on October 13, 2026