Skip to main content
POST
Enrich a stack trace

Restrictions

Usage

  • type defaults to browser when omitted for backward compatibility.
  • Set near from 1 to 20 to include source-code snippets around converted frames.
  • For Android NDK native crashes, provide arch and source_type: ndk so the backend routes to native symbolication.
  • For iOS crash stacks, pass binary_images so addresses can be relocated against the uploaded dSYM files.
  • no_cache is intended for debugging and bypasses cached enrich results.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Stack trace enrichment request.

service
string
required

Application or service name used when the sourcemap was uploaded.

version
string
required

Application version used when the sourcemap was uploaded.

arch
string

Android NDK architecture such as arm, arm64, x86, or x64.

binary_images
object[]

Loaded binary images from an iOS crash report.

build_id
string

Android build ID for Gradle plugin 1.13.0 and later.

near
integer

Number of nearby meaningful source lines to return around converted frames.

Required range: 1 <= x <= 20
no_cache
boolean

Skip cached enrich results. Intended for debugging.

platform
enum<string>

Narrows a react-native enrich to the app's native platform: ios for the iOS native layer, android for the Android native layer (the console derives it from the event's OS). Ignored for other type values.

Available options:
ios,
android
source_type
string

Android error source type. Use ndk with arch for native symbolication.

stack
string

Raw stack trace to parse and enrich.

type
enum<string>

Source platform whose symbol store is used. Defaults to browser when omitted.

Available options:
browser,
android,
ios,
miniprogram,
harmony,
flutter,
electron,
react-native
variant
string

Android build variant used by older Gradle plugin versions.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

data
object
required

Enriched stack frames.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"