Crashes

Get crash list

The crash list API retrieves crash data for your application with flexible filtering and pagination options. This endpoint allows you to query crashes by date range, platform, app version, and environment mode, making it easy to analyze crash patterns and trends across different segments of your application.

By default, the API returns the first 500 production crashes across all platforms and app versions. Use the filtering parameters to narrow down results or pagination parameters to retrieve additional records.
OAuth Scope : JProxy.jmobileapi.ALL

Query Parameters

Get crash count by date

The crash count by date API provides aggregated crash statistics organized by date (in epoch format) and platform. This endpoint returns time-series data showing crash counts, issue counts, device counts, and user counts for each day within the specified date range, making it ideal for trend analysis and crash monitoring dashboards.

By default, the API returns crash count data for all app versions across all platforms within the specified date range. Users can optionally apply platform and app version filters to narrow down the results to specific segments of their application.
OAuth Scope : JProxy.jmobileapi.ALL

Query Parameters

Get crash count by date (timezone)

Query Parameters

Get crash count summary

The crash count summary API provides comprehensive crash statistics for a specified date range along with comparative data from the equivalent previous period. This endpoint delivers aggregated crash metrics including total crash occurrences, unique issues count, affected users, impacted devices, and app version breakdowns, making it ideal for executive dashboards and performance analysis. The API includes a precrashcount object that provides comparative data from the previous equivalent period. For example, if requesting crash summary for the last 7 days, precrashcount contains data from the 7 days immediately before that period. This enables easy calculation of growth rates, trend identification, and period-over-period performance analysis.

By default, the API returns crash summary data for all app versions across all platforms within the specified date range. Users can optionally apply platform and app version filters to focus on specific segments of their application
OAuth Scope : JProxy.jmobileapi.ALL

Query Parameters

Get crash detail

The crash detail API retrieves comprehensive information about a specific crash instance using its unique identifier. This endpoint provides in-depth crash data including exception details, device information, user context, and technical metadata, making it essential for debugging and root cause analysis. The API requires a unique crash identifier (uniqueid) obtained from the crash list API, along with a date range to scope the search. It returns detailed crash information including the crash date, exception type and message, stack trace, affected screen or activity, network status, device specifications, operating system version, app version details, user information, session data, and custom properties.

By default, the API searches across all app versions but can be filtered to specific versions using the appversion parameter (maximum 1 values). The response includes technical details such as the crash unique message ID, app release version, bundle name, issue count, process ID, device orientation, and timestamps for when the crash occurred.
OAuth Scope : JProxy.jmobileapi.ALL

Path Parameters

Query Parameters

Device specific crash distribution

The crash distribution by device model API provides crash statistics grouped by device model for a specific crash issue. This endpoint analyzes how a particular crash is distributed across different device types, helping identify device-specific crash patterns and hardware-related stability issues. The API requires a unique crash identifier (uniqueid) obtained from the crash list API, along with a date range to scope the analysis. It returns a breakdown showing which device models are most affected by the specific crash, including the crash count for each device model. This data is essential for identifying whether crashes are concentrated on particular devices, which can indicate hardware compatibility issues, device-specific bugs, or performance problems on certain device configurations.

By default, the API analyzes data across all app versions but can be filtered to specific versions using the appversion parameter (maximum 1 value). The response includes pagination support with configurable limit (default and maximum 500) and offset parameters for handling large datasets when many device models are affected.
OAuth Scope : JProxy.jmobileapi.ALL

Path Parameters

Query Parameters

OS version specific crash distribution

The OS version specific crash distribution API analyzes how a particular crash is distributed across different operating system versions. This endpoint takes a unique crash identifier and returns crash counts grouped by OS version, helping identify version-specific compatibility issues and stability patterns. The API requires a crash unique identifier and date range, with optional filtering by app versions. It returns data showing which OS versions are most affected by the specific crash, enabling teams to identify problematic OS versions, prioritize compatibility testing, and make informed decisions about minimum OS support requirements. Perfect for debugging version-specific issues and understanding crash impact across the OS ecosystem.
OAuth Scope : JProxy.jmobileapi.ALL

Path Parameters

Query Parameters

Affected devices

The list of affected devices API retrieves detailed information about all devices impacted by a specific crash within a given time period. This endpoint provides device-level insights for crash analysis, showing which individual devices experienced a particular crash issue along with their technical specifications and user context. The API requires a unique crash identifier and date range, returning device details including app version, user ID, device ID, device model, OS version, and crash occurrence timestamps. Optional app version filtering allows analysis of version-specific device impact. With pagination support (default 500 records), the endpoint handles crashes affecting large numbers of devices.
OAuth Scope : JProxy.jmobileapi.ALL

Path Parameters

Query Parameters

Unique crash count by date

The unique crash count by date API provides time-series data showing the frequency of a specific crash over time. This endpoint tracks how often a particular crash occurs on a daily basis within the specified date range, enabling teams to monitor crash trends, identify spikes, and assess the effectiveness of fixes for specific issues. The API requires a unique crash identifier and date range, with optional filtering by app versions and platforms. It returns daily crash counts, unique issues, affected devices, and impacted users organized by date, allowing teams to visualize crash frequency patterns and correlate them with app releases, updates, or external factors.
OAuth Scope : JProxy.jmobileapi.ALL

Path Parameters

Query Parameters

Unique crash count by date (timezone)

The unique crash count by date (timezone) API provides timezone-aware time-series data for a specific crash, showing how frequently that particular crash occurs over time with configurable granularity. This endpoint tracks crash occurrence patterns for individual issues, enabling teams to monitor specific crash trends in localized time contexts. The API requires a unique crash identifier, date range, timezone, and time granularity settings. It returns crash counts, issue counts, device counts, and user counts organized by the specified time intervals (daily, hourly, 3-hour, or 6-hour periods) in the target timezone. Optional filtering by app versions and platforms allows focused analysis of crash patterns.
OAuth Scope : JProxy.jmobileapi.ALL

Path Parameters

Query Parameters