• Home
  • Dynatrace API
  • Configuration
  • RUM
  • Mobile and custom app
  • Apps
  • PUT an app

Mobile and custom app API - PUT an app

Updates the specified mobile or custom app.

The request consumes and produces an application/json payload.

PUTManaged https://{your-domain}/e/{your-environment-id}/api/config/v1/applications/mobile/{id}
SaaS https://{your-environment-id}.live.dynatrace.com/api/config/v1/applications/mobile/{id}
Environment ActiveGate https://{your-activegate-domain}/e/{your-environment-id}/api/config/v1/applications/mobile/{id}

Authentication

To execute this request, you need an access token with Write configuration (WriteConfig) scope. To learn how to obtain and use it, see Tokens and authentication.

Parameters

ParameterTypeDescriptionInRequired
idstring

The ID of the application to be updated.

pathrequired
bodyMobileCustomAppConfig

The JSON body of the request. Contains updated configuration of the mobile or custom application.

Do not set the identifier in the body.

bodyoptional

Request body objects

The MobileCustomAppConfig object

Configuration of an existing mobile or custom application.

ElementTypeDescription
identifierstring

The Dynatrace entity ID of the application.

Can be null.

namestring

The name of the application.

applicationTypestring

The type of the application.

The element can hold these values
  • CUSTOM_APPLICATION
  • MOBILE_APPLICATION

Can be null.

applicationIdstring

The UUID of the application.

It is used only by OneAgent to send data to Dynatrace.

Can be null.

iconTypestring

Custom application icon.

Mobile apps always use the mobile device icon, so this icon can only be set for custom apps.

The element can hold these values
  • AMAZON_ECHO
  • DESKTOP
  • EMBEDDED
  • IOT
  • MICROSOFT_HOLOLENS
  • UFO
  • USERS

Can be null.

costControlUserSessionPercentageinteger

The percentage of user sessions to be analyzed.

apdexSettingsMobileCustomApdex

Apdex configuration of a mobile or custom application.

A duration less than the tolerable threshold is considered satisfied.

optInModeEnabledboolean

The opt-in mode is enabled (true) or disabled (false).

This value is only applicable to mobile and not to custom apps.

Can be null.

sessionReplayEnabledboolean

The session replay is enabled (true) or disabled (false). This value is only applicable to mobile and not to custom apps.

Can be null.

sessionReplayOnCrashEnabledboolean

Deprecated. Please use sessionReplayEnabled to enable or disable session replay for mobile apps.

Can be null.

beaconEndpointTypestring

The type of the beacon endpoint.

The element can hold these values
  • CLUSTER_ACTIVE_GATE
  • ENVIRONMENT_ACTIVE_GATE
  • INSTRUMENTED_WEB_SERVER
beaconEndpointUrlstring

The URL of the beacon endpoint.

Only applicable when the beaconEndpointType is set to ENVIRONMENT_ACTIVE_GATE or INSTRUMENTED_WEB_SERVER.

Can be null.

The MobileCustomApdex object

Apdex configuration of a mobile or custom application.

A duration less than the tolerable threshold is considered satisfied.

ElementTypeDescription
toleratedThresholdinteger

Apdex tolerable threshold, in milliseconds: a duration greater than or equal to this value is considered tolerable.

frustratingThresholdinteger

Apdex frustrated threshold, in milliseconds: a duration greater than or equal to this value is considered frustrated.

frustratedOnErrorboolean

Apdex error condition: if true the user session is considered frustrated when an error is reported.

Request body JSON model

This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.

json
{
  "identifier": "string",
  "name": "string",
  "applicationType": "CUSTOM_APPLICATION",
  "applicationId": "string",
  "iconType": "AMAZON_ECHO",
  "costControlUserSessionPercentage": 1,
  "apdexSettings": {
    "toleratedThreshold": 1,
    "frustratingThreshold": 1,
    "frustratedOnError": true
  },
  "optInModeEnabled": true,
  "sessionReplayEnabled": true,
  "sessionReplayOnCrashEnabled": true,
  "beaconEndpointType": "CLUSTER_ACTIVE_GATE",
  "beaconEndpointUrl": "string"
}

Response

Response codes

CodeTypeDescription
204-

Success. The application has been updated. Response doesn't have a body.

400ErrorEnvelope

Failed. The input is invalid.

404-

Failed. The specified entity doesn't exist.

Validate payload

We recommend that you validate the payload before submitting it with an actual request. A response code of 204 indicates a valid payload.

The request consumes an application/json payload.

POSTManaged https://{your-domain}/e/{your-environment-id}/api/config/v1/applications/mobile/{id}/validator
SaaS https://{your-environment-id}.live.dynatrace.com/api/config/v1/applications/mobile/{id}/validator
Environment ActiveGate https://{your-activegate-domain}/e/{your-environment-id}/api/config/v1/applications/mobile/{id}/validator

Authentication

To execute this request, you need an access token with Write configuration (WriteConfig) scope. To learn how to obtain and use it, see Tokens and authentication.

Response

Response codes

CodeTypeDescription
204-

Success. The submitted configuration is valid. Response doesn't have a body.

400ErrorEnvelope

Failed. The input is invalid.