Try it free

Settings API - POST transfer ownership

  • Reference
  • Published Jul 09, 2026

Transfers ownership of the specified settings object. Only the current owner or a user with the settings:objects:admin permission (globally or for the relevant schema) can transfer ownership. The previous owner loses access after the transfer unless they are explicitly listed as an accessor on the object.

This endpoint applies only to objects on schemas with owner-based access control enabled (ownerBasedAccessControl: true). To identify such schemas, include ownerBasedAccessControl in the add-fields parameter when calling List schemas.

The request consumes and produces an application/json payload.

POSTManagedDynatrace for Governmenthttps://{your-domain}/e/{your-environment-id}/v2/settings/objects/{objectId}:transfer-ownership
POSTEnvironment ActiveGatehttps://{your-activegate-domain}/e/{your-environment-id}/v2/settings/objects/{objectId}:transfer-ownership

Parameters

ParameterTypeDescriptionInRequired
objectIdstring

The ID of the required settings object.

pathRequired
adminAccessboolean

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
bodyTransferOwnershipRequest

The JSON body of the request.

bodyOptional

Request body objects

The TransferOwnershipRequest object

The request to change ownership of an object.

ElementTypeDescriptionRequired
newOwnerIdentity

An Identity describing either a user, a group, or the all-users group (applying to all users).

Optional

The Identity object

An Identity describing either a user, a group, or the all-users group (applying to all users).

ElementTypeDescriptionRequired
idstring

The user id or user group id if type is 'user' or 'group', missing if type is 'all-users'.

Optional
typestring

The type of the identity.

The element can hold these values
  • all-users
  • group
  • user
Required

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.

{
  "newOwner": {
    "id": "string",
    "type": "user"
  }
}

Response

Response codes

CodeTypeDescription
204-

Success. Response doesn't have a body.

400ErrorEnvelope

Failed. The input is invalid.

403ErrorEnvelope

Failed. Forbidden.

404ErrorEnvelope

No object available for the given objectId.

4XXErrorEnvelope

Client side error.

5XXErrorEnvelope

Server side error.

Response body objects

The ErrorEnvelope object

ElementTypeDescription
errorError-

The Error object

ElementTypeDescription
codeinteger

The HTTP status code

constraintViolationsConstraintViolation[]

A list of constraint violations

messagestring

The error message

The ConstraintViolation object

A list of constraint violations

ElementTypeDescription
locationstring-
messagestring-
parameterLocationstring-
The element can hold these values
  • HEADER
  • PATH
  • PAYLOAD_BODY
  • QUERY
pathstring-

Response body JSON models

{
  "error": {
    "code": 1,
    "constraintViolations": [
      {
        "location": "string",
        "message": "string",
        "parameterLocation": "HEADER",
        "path": "string"
      }
    ],
    "message": "string"
  }
}