Try it free

Update a settings object

  • Latest Dynatrace
  • Reference
  • Published Oct 13, 2026

Update an existing Dynatrace settings object with new values with the Settings API, using optimistic locking to detect simultaneous changes.

PUTSaaShttps://{your-environment-id}.apps.dynatrace.com/platform/settings/v1/objects/{object-id}

Overview

You use the object-id path parameter to choose a settings object and send its new values in the request body. The required optimistic-locking-version query parameter must match the stored version, which detects simultaneous changes. To change a secret property, send its new value unmasked; to keep it, send the current masked value.

Authentication

To execute this request, you need a platform token or OAuth access token with settings:objects:write scope. To learn how to obtain and use it, see Tokens and authentication.

Parameters

ParameterTypeDescriptionInRequired
object-idstring

The ID of the required settings object

pathRequired
optimistic-locking-versionstring

The version of the object for optimistic locking. You can use it to detect simultaneous modifications by different users.

It's generated upon retrieval (GET requests). If set on update (PUT request) or deletion, the update/deletion will be allowed only if there wasn't any change between the retrieval and the update.

queryRequired
admin-accessboolean

If set to true and user has settings:objects:admin permission, the endpoint will act as if the user is the owner of all objects

queryOptional
validate-onlyboolean

If true, the request runs only validation of the submitted settings object, without saving it.

queryOptional
bodySettingsObjectUpdate

The JSON body of the request. Contains the updated parameters of the settings object.

bodyRequired

Request body objects

The SettingsObjectUpdate object

An update of a settings object.

ElementTypeDescriptionRequired
valueSettingsValue

The value of the setting.

It defines the actual values of settings' parameters.

The actual content depends on the object's schema.

Required
insertPositionstring-
The element can hold these values
  • first
  • last
  • after
  • before
Optional
insertNeighborstring

The position of the new object based on the objectId of the neighbor. Only for insertPosition afterand before

Optional
schemaVersionstring

The version of the schema on which the object is based.

Optional
externalIdstring

External identifier for the object being updated

Optional

The SettingsValue object

The value of the setting.

It defines the actual values of settings' parameters.

The actual content depends on the object's schema.

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.

{
"value": {
"autoMonitoring": true
},
"insertPosition": "first",
"insertNeighbor": "Y2ktaGdyb3VwLTEyMythZjhjOThlOS0wN2I0LTMyMGEtOTQzNi02NTEyMmVlNWY4NGQ=",
"schemaVersion": "1.0.0",
"externalId": "string"
}

Response

Response codes

CodeTypeDescription
200SettingsUpdateResponse

Success.

204-

Success. No validation errors.

400--
403--
404--
409--
429--
503--
4XX--
5XX--

Response body objects

The SettingsUpdateResponse object

The response to an update request.

ElementTypeDescription
versionstring

The version of the object for optimistic locking. You can use it to detect simultaneous modifications by different users.

It's generated upon retrieval (GET requests). If set on update (PUT request) or deletion, the update/deletion will be allowed only if there wasn't any change between the retrieval and the update.

Response body JSON models

{
"version": "Y2ktaGdyb3VwLTEyMythZjhjOThlOS0wN2I0LTMyMGEtOTQzNi02NTEyMmVlNWY4NGQ="
}
Related tags
Platform APIDynatrace Platform