Skip to main content
POST
Update application

Restrictions

Usage

  • links.systems[].url must start with http or https; ${var} tokens are resolved from RUM event context.
  • links.systems[].event_types accepts: crash, error, view, action, resource, session, all.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

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

Parameters for updating a RUM application. All fields except application_id are optional.

application_id
string
required

Application ID to update. Get application IDs via POST /rum/application/list.

application_name
string

New application name, 1–40 characters. Omit to leave unchanged.

type
enum<string>

Application type. Omit to leave unchanged. Platform identifier, one of browser (web), ios, android, react-native, flutter, kotlin-multiplatform, roku, unity, miniprogram (WeChat mini program), harmony (HarmonyOS), electron.

Available options:
browser,
ios,
android,
react-native,
flutter,
kotlin-multiplatform,
roku,
unity,
miniprogram,
harmony,
electron
team_id
integer<int64>

Owning team ID. Get team IDs via POST /team/list. Omit to leave unchanged.

is_private
boolean | null

Restrict access to members of the owning team; false explicitly makes the application public. Omit to leave unchanged.

no_ip
boolean | null

When true, stop collecting user IP addresses; when false, resume collecting them. Omit to leave unchanged.

no_geo
boolean | null

When true, stop inferring geographic location from IP; when false, resume inferring it. Omit to leave unchanged.

alerting
object

Alerting configuration. Omit to leave unchanged.

tracing
object

APM tracing integration configuration. Omit to leave unchanged.

External-link integration configuration. Omit to leave unchanged.

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.

request_id
string
required

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

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object
required

Empty response body. The server returns data: null on success.