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
This guide includes reference information for you to use to integrate the Vitals API. Use of the Vitals API is subject to the Program Materials License Agreement.

Prerequisites

Before making API calls, make sure you meet the following requirements:

Base URL

The base URL of the Vitals API is https://developer.amazon.com/api/appstore.

Operations

The Vitals API includes the following operations and endpoints:

Request

See the following sections for details on the parameters and validation rules.

Request parameters

Every query request must include the following parameters:

Response

See the following sections for details on the response fields.

Response fields

Successful response (200)

Implementation examples

The following examples show Python code for various tasks using the Vitals API.

Obtain access token

Use your client ID and client secret to obtain an auth token. You must add the auth token to the header of each API request. The following example shows how to obtain an auth token and create the Authorization header using the token.

Check data freshness

The following example shows how to check the latest available data timestamp before querying.

GET freshness response example

Convert local time to UTC

The following example shows how to convert a local datetime to UTC.

Query metrics

The following example shows the full shape of a query against a rate metric set (crash, ANR, LMK). Comments call out which fields are required vs. optional.

Paginate through results

The following example shows how to fetch all results when the response includes a nextPageToken.

Query top crash issues

The issuesMetricSet returns top crash/ANR/LMK issues ranked by frequency. Unlike rate metric sets, it aggregates over the entire time range and returns one row per unique crash signature with its stacktrace. ReportType specifies CRASH or ANR for the shared stacktraces.

Error handling

See the following sections for how to handle errors.

Error response format

All errors return structured JSON:

Error codes

Common mistakes and fixes

Retries and best practices

See the following sections for retry strategy and best practices.

Retry strategy example

Production best practices

Last modified on October 13, 2026