Skip to main content
POST
Update application

Restrictions

Usage

  • 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.

application_name
string | null

New application name.

type
enum<string> | null
Available options:
browser,
ios,
android,
react-native,
flutter,
kotlin-multiplatform,
roku,
unity
team_id
integer<int64> | null
is_private
boolean | null
no_ip
boolean | null
no_geo
boolean | null
alerting
object

Alert settings for the application.

tracing
object

APM tracing integration settings.

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.