Try it free

Resolve effective settings permissions

  • Latest Dynatrace
  • Reference
  • Published Oct 13, 2026

Resolve the calling user's effective settings permissions in Dynatrace with the App Settings API from a permissions request body.

POSTSaaShttps://{your-environment-id}.apps.dynatrace.com/v2/effective-permissions:resolve

Overview

You send a permissions request body to resolve the calling user's effective settings permissions in the environment. Dynatrace returns success for the App Settings API operation when the request is accepted.

Authentication

To execute this request, you need a platform token or OAuth access token with all of the following scopes:

  • app-settings:objects:read
  • app-settings:objects:write

To learn how to obtain and use it, see Tokens and authentication.

Parameters

ParameterTypeDescriptionInRequired
bodyResolutionRequest-bodyRequired

Request body objects

The ResolutionRequest object

ElementTypeDescriptionRequired
permissionsSinglePermissionRequest[]-Required

The SinglePermissionRequest object

optional generic set of context data

ElementTypeDescriptionRequired
permissionstring-
The element can hold these values
  • app-settings:objects:read
  • app-settings:objects:write
  • app-settings:objects:admin
Required
contextPermissionContext-Optional

The PermissionContext object

ElementTypeDescriptionRequired
schemaIdstring-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.

{
"permissions": [
{
"permission": "app-settings:objects:read",
"context": {
"schemaId": "string"
}
}
]
}

Response

Response codes

CodeTypeDescription
200--
400ErrorResponse

Failed. The input is invalid.

403ErrorResponse

Failed. Forbidden. No access to any schema.

4XX--
5XX--

Response body objects

The ErrorResponse object

ElementTypeDescription
errorError

Standard error response

The Error object

Standard error response

ElementTypeDescription
codenumber

The error code (HTTP response)

messagestring

The error message

retryAfterSecondsnumber

Number of seconds a request can be retried after a 'too many requests' error response.

detailsErrorDetails

Optional details of the error

The ErrorDetails object

Optional details of the error

ElementTypeDescription
errorRefstring

reference to the error occurrence in the internal self-monitoring, logging, etc.

constraintViolationsConstraintViolation[]

A list of constraint violations of input parameters (path, query, request body)

missingScopesstring[]

In case of a 403 - Forbidden response, a list of missing scopes necessary to successfully execute the request

The ConstraintViolation object

Contains information about a constraint violation caused by invalid input.

ElementTypeDescription
pathstring

The path of the parameter that caused the constraint violation

messagestring

The constraint violation description message

parameterLocationstring

Describes the general location of the violating parameter

The element can hold these values
  • PATH
  • QUERY
  • HEADER
  • PAYLOAD_BODY

Response body JSON models

{
"error": {
"code": 1,
"message": "string",
"retryAfterSeconds": 1,
"details": {
"errorRef": "string",
"constraintViolations": [
{
"path": "string",
"message": "string",
"parameterLocation": "PATH"
}
],
"missingScopes": [
"string"
]
}
}
}
Related tags
Platform APIDynatrace Platform