Reporting API Explorer

The Reporting API Explorer is an interactive query builder on the developer portal. You can use it to explore Reporting and Vitals API metrics, construct requests visually, and execute them against live data, all without having to write any code. Use the API explorer for initial exploration.

The API explorer generates the following for you:

• Full JSON response inline
• Copy-ready request cURL command Code snippets in Java, Python, and Node.js

You can then perform the following actions:

• Select a metric set, pick metrics and dimensions, apply filters, and run queries, all through a visual interface
• See the generated API request update in real time as you configure options
• Inspect the full JSON response inline
• Copy the request to use in your own code

• Use the API Explorer
  • 1. Select your app package name
  • 2. Select a metric set
  • 3. Choose aggregation and time period
  • 4. Pick metrics
  • 5. Optional: Add dimensions
  • 6. Optional: Apply filters
  • 7. Set page size
  • 8. Run the query
• Request Preview panel
• Response panel
• Tips
• Related topics

Use the API Explorer

You can access the API explorer from the API Access tab in the App Analytics section of the developer portal.

See the following steps on how to use the Reporting API Explorer.

1. Select your app package name

Select or enter your Android package name (for example, com.amazon.sampleapp) in the App field. This must be an app owned by your vendor account.

2. Select a metric set

From the Metric Set dropdown, choose a metric set to query:

Metric Set	What it measures
Crash	Crash rate, user-perceived crash rate, and crash event counts
ANR	ANR rate, user-perceived ANR rate, and ANR event counts
LMK	LMK rate, user-perceived LMK rate, and LMK event counts
Issues	Top crash/ANR/LMK issues ranked by frequency with stacktraces

3. Choose aggregation and time period

• Aggregation: Select HOURLY or DAILY.
• Time Period: Choose "Last 7 days" for a quick query, or "Custom date range" to specify exact dates.

4. Pick metrics

Use the Metrics multi-select dropdown to choose which metrics to include. Leave empty to query all metrics for the selected metric set.

Available metrics vary by metric set. For example, the LMK metric set offers the following metrics:

• lmkRate
• lmkRate7dUserWeighted
• lmkRate28dUserWeighted
• userPerceivedLmkRate
• userPerceivedLmkRate7dUserWeighted
• userPerceivedLmkRate28dUserWeighted
• distinctDevices
• lmkCount

5. Optional: Add dimensions

Select dimensions to break down results. Each dimension adds a column to the output. Available dimensions include the following:

• Version Code
• Country Code
• Device Model
• Device Type
• Device OS
• OS Version

6. Optional: Apply filters

Narrow results without adding breakdowns by setting filter values:

• Version Code: Filter to a specific app version
• Country: Filter to specific countries (for example, US)
• Device Model: Filter to specific device models
• Device Type: Filter by AMAZON_FIRE_TV or AMAZON_TABLETS
• Device OS: Filter by Fire OS or Vega OS devices
• OS Version: Filter by OS version

7. Set page size

Choose the maximum number of rows per response (default: 1000, max: 100,000).

8. Run the query

Click Run Query to execute. The response appears in the Response panel on the right.

Request Preview panel

As you configure your query, the Request Preview panel updates in real time showing:

• The full POST URL
• The complete cURL command and JSON request body

You can expand the preview into a full-screen modal for easier reading, or copy it to your clipboard using the copy button.

Response panel

After running a query, the Response panel displays the full JSON response including:

• rows[] with time periods, dimension values, and metric values
• Pagination token (if more results are available)

You can expand the response into a full-screen modal to inspect large result sets.

Tips

See the following tips for using the Reporting API Explorer:

• Start simple: Run a query with no dimensions or filters first to verify your app has data, then add breakdowns.
• Check freshness: If you get empty results, your selected time range may be ahead of available data. Try an earlier date range.
• Copy and integrate: Use the Request Preview to copy the exact request into your app code.
• 28-day metrics require DAILY: If you select a 28-day user-weighted metric, switch aggregation to DAILY (these are not available for HOURLY).
• Count vs. Rate: Use crashCount/anrCount/lmkCount for absolute event volumes. Use rate metrics for normalized trend comparison across versions or devices.

Related topics

• Reporting API: Sales, earnings, and subscription report downloads
• Vitals API Overview: Available metrics, dimensions, and FAQ
• Vitals API Reference: Authentication, endpoints, code examples, and error handling

---

Last updated: Jun 29, 2026