Dynatrace · Schema
UserListDto
AI OperationsAnalyticsAPMApplication Performance MonitoringApplication SecurityAutomationCloud MonitoringDigital Experience ManagementIntelligenceObservabilityMonitoring
Properties
| Name | Type | Description |
|---|---|---|
| count | number | The number of entries in the list. |
| items | array | A list of the account's users. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/dynatrace/main/json-schema/dynatrace-user-list-dto-schema.json",
"title": "UserListDto",
"x-generated": "2026-10-04",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/dynatrace-user-management-api-openapi.yml#/components/schemas/UserListDto",
"type": "object",
"properties": {
"count": {
"type": "number",
"description": "The number of entries in the list."
},
"items": {
"description": "A list of the account's users.",
"type": "array",
"items": {
"$ref": "#/$defs/UsersDto"
}
}
},
"required": [
"count",
"items"
],
"$defs": {
"UserLoginMetaDataDto": {
"type": "object",
"properties": {
"successfulLoginCounter": {
"type": "number",
"description": "The number of successful sign-ins."
},
"failedLoginCounter": {
"type": "number",
"description": "The number of failed sign-ins."
},
"lastSuccessfulLogin": {
"type": "string",
"description": "The date and time of the most recent successful sign-in in `2021-05-01T15:11:00Z` format."
},
"lastFailedLogin": {
"type": "string",
"description": "The date and time of the most recent failed sign-in in `2021-05-01T15:11:00Z` format."
},
"createdAt": {
"type": "string",
"description": "The date and time of user creation in `2021-05-01T15:11:00Z` format."
},
"updatedAt": {
"type": "string",
"description": "The date and time of the most recent modification to the user in `2021-05-01T15:11:00Z` format."
}
},
"required": [
"successfulLoginCounter",
"failedLoginCounter",
"lastSuccessfulLogin",
"lastFailedLogin",
"createdAt",
"updatedAt"
]
},
"UsersDto": {
"type": "object",
"properties": {
"uid": {
"type": "string",
"description": "The UUID of the user."
},
"email": {
"type": "string",
"description": "The email address of the user."
},
"name": {
"type": "string",
"description": "The first name of the user."
},
"surname": {
"type": "string",
"description": "The last name of the user."
},
"userStatus": {
"type": "string",
"enum": [
"ACTIVE",
"INACTIVE",
"PENDING",
"DELETED",
"ECUSTOMS_MANUALLY_BLOCKED"
],
"description": "The status of this user in Dynatrace: \n\n* `ACTIVE`: The user is active.\n* `INACTIVE`: The user is deactivated and cannot sign in to Dynatrace. \n* `PENDING`: The user received an invitation, but hasn't completed sign-up yet. \n* `DELETED`: The user was deleted and cannot sign in to Dynatrace anymore. \n* `ECUSTOMS_MANUALLY_BLOCKED`: The user is blocked due to to a trade and export compliance violation. \n"
},
"emergencyContact": {
"type": "boolean",
"description": "The user is (`true`) or is not (`false`) an emergency contact for the account."
},
"userLoginMetadata": {
"description": "Available if user has logged into Dynatrace at least once",
"allOf": [
{
"$ref": "#/$defs/UserLoginMetaDataDto"
}
]
}
},
"required": [
"uid",
"email"
]
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/dynatrace-user-list-dto"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.