• /
  • EnglishEspañol日本語한국어Português
  • Log inStart now

Mobile crash REST API v1

The mobile crash API is a RESTful way to retrieve information about your mobile application crashes that have been reported to New Relic. It brings together the attributes and thread data available for a given set of crash types and occurrences.

You can use the API to:

  1. GET your most recent crash types
  2. GET a list of occurrence IDs from a single crash type
  3. GET Thread, Library and Attributes for a particular occurrence ID

Contents

Prerequisites

To use the Crash API in these examples, you need:

  • Your New Relic Crash API Key. Pass this key as the value of the X-API-KEY header.
  • Your New Relic account ID
  • Your mobile monitoring application ID

For example:

https://rpm.newrelic.com/accounts/{account_ID}/mobile/{mobile_application_ID}

Tip

Note: X-API-KEYs are rate limited to 600 requests per minute.

GET mobile-crashes/

Purpose: Returns the most recent crash types.

GET mobile-crashes/:crash_fingerprint

Purpose: Returns details about recent crash fingerprints.

GET crash-details/:occurrence_id

Purpose: Returns details about a specific crash occurrence.

Tip

Note: Time period matters! If you do not get any crash details for an occurrence, try expanding your start and end times.

GET thread-data/:crash_fingerprint

Purpose: Returns symbolicated (iOS) or deobfuscated (Android) thread data for a given crash fingerprint.

Response Codes

Status Code

General Meaning

Description

400

Bad Request

Malformed or missing request parameters.

401

Unauthorized

Missing an API key or bad API key

403

Forbidden

API access not enabled

404

Not Found

Requested resource ID not found

406

Not Acceptable

Client requested an unsupported content type

422

Unprocessable Entity

Validation error

500

Internal Server Error

A server error has occurred

200

Success

Response returned

Copyright © 2024 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.