Skip to main content
POST
Update application

Restrictions

Usage

  • Only fields present in the request are changed. alerting, tracing and links replace the whole stored object when sent; repositories replaces the whole list.
  • When tracing is sent, open_type (popup or tab) and an http/https endpoint are required even if enabled is false.
  • links.systems[].url must start with http or https; each system needs a name and at least one event_types entry.
  • When alerting is sent with delivery_mode oncall, the existing integration_id is kept (or one is assigned); a client-supplied integration_id is ignored.
  • An unknown or deleted application_id returns InvalidParameter. The caller must be able to edit the application: the account owner, an account admin, the application’s creator, or a member of its owning team; anyone else gets AccessDenied.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

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.

alerting
object

Alerting configuration. When sent, it replaces the stored alerting object (except integration_id, which the server manages). Omit to leave unchanged.

application_name
string | null

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

Required string length: 1 - 40
is_private
boolean | null

true limits access to the account owner, account admins, the creator and members of the owning team; false makes the application visible to everyone in the account. Omit to leave unchanged.

External-link integration configuration. When sent, it replaces the stored object, including the whole systems list. Omit to leave unchanged.

repositories
object[]

Replaces the linked source code repositories when present; an empty array removes all links, and omitting the field leaves them unchanged. At most 10 entries.

Maximum array length: 10
no_geo
boolean | null

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

no_ip
boolean | null

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

team_id
integer<int64> | null

New owning team ID. Get team IDs via POST /team/list. Omit to leave unchanged. Moving the application to another team changes who can edit it.

tracing
object

APM tracing integration configuration. When sent, it replaces the stored object and must carry a valid open_type and endpoint. Omit to leave unchanged.

type
enum<string> | null

Application type. Omit to leave unchanged. Platform identifier:

Available options:
browser,
ios,
android,
react-native,
flutter,
kotlin-multiplatform,
roku,
unity,
miniprogram,
harmony,
electron

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

No payload. Depending on the operation, data is {} or omitted from the envelope; rely only on the HTTP 200 status and the absence of error.