Update application
Update an existing RUM application. All fields except application_id are optional — only provided fields are updated.
Restrictions
Usage
links.systems[].urlmust start withhttporhttps;${var}tokens are resolved from RUM event context.links.systems[].event_typesaccepts: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 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
Parameters for updating a RUM application. All fields except application_id are optional.
Application ID to update. Get application IDs via POST /rum/application/list.
New application name, 1–40 characters. Omit to leave unchanged.
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.
browser, ios, android, react-native, flutter, kotlin-multiplatform, roku, unity, miniprogram, harmony, electron Owning team ID. Get team IDs via POST /team/list. Omit to leave unchanged.
Restrict access to members of the owning team; false explicitly makes the application public. Omit to leave unchanged.
When true, stop collecting user IP addresses; when false, resume collecting them. Omit to leave unchanged.
When true, stop inferring geographic location from IP; when false, resume inferring it. Omit to leave unchanged.
Alerting configuration. Omit to leave unchanged.
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.