Dynatrace · JSON Structure

Problems Webhook Notification Config Structure

Configuration for a webhook notification integration in Dynatrace. Posted to POST /api/config/v1/notifications to register the webhook.

Type: object Properties: 8 Required: 5
AI OperationsAnalyticsAPMApplication Performance MonitoringApplication SecurityAutomationCloud MonitoringDigital Experience ManagementIntelligenceObservability

WebhookNotificationConfig is a JSON Structure definition published by Dynatrace, describing 8 properties, of which 5 are required. It conforms to the https://json-structure.org/meta/core/v0/# meta-schema.

Properties

type name active url alertingProfile headers acceptAnyCertificate payload

Meta-schema: https://json-structure.org/meta/core/v0/#

JSON Structure

Raw ↑
{
  "$schema": "https://json-structure.org/meta/core/v0/#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/dynatrace/refs/heads/main/json-structure/problems-webhook-notification-config-structure.json",
  "description": "Configuration for a webhook notification integration in Dynatrace. Posted to POST /api/config/v1/notifications to register the webhook.",
  "type": "object",
  "properties": {
    "type": {
      "type": "string",
      "description": "The notification type. Must be WEBHOOK for webhook integrations.",
      "enum": [
        "WEBHOOK"
      ],
      "example": "WEBHOOK"
    },
    "name": {
      "type": "string",
      "description": "A display name for this notification configuration.",
      "example": "My Problem Webhook"
    },
    "active": {
      "type": "boolean",
      "description": "Whether this notification integration is active.",
      "example": true
    },
    "url": {
      "type": "uri",
      "description": "The HTTPS URL of the webhook endpoint that will receive problem notifications.",
      "example": "https://webhook.example.com/webhook/dynatrace/problems"
    },
    "alertingProfile": {
      "type": "string",
      "description": "The ID of the alerting profile (problem filter) that controls which problems trigger this notification.",
      "example": "alerting-profile-uuid"
    },
    "headers": {
      "type": "array",
      "description": "Optional HTTP headers to include in the webhook request, such as authorization headers or content-type overrides.",
      "items": {
        "$ref": "#/components/schemas/WebhookHeader"
      },
      "example": [
        {
          "name": "Authorization",
          "value": "Bearer my-secret-token"
        }
      ]
    },
    "acceptAnyCertificate": {
      "type": "boolean",
      "description": "Whether to accept any TLS certificate from the webhook endpoint. Should be false in production environments.",
      "example": false
    },
    "payload": {
      "type": "string",
      "description": "The custom payload template using Dynatrace placeholder variables such as {ProblemID}, {ProblemTitle}, {State}. If not specified, Dynatrace uses the default JSON payload format.",
      "example": "example-value"
    }
  },
  "required": [
    "type",
    "name",
    "active",
    "url",
    "alertingProfile"
  ],
  "name": "WebhookNotificationConfig"
}

Work with this as data

Every JSON Structure 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 json structure

4 MCP tools reach this
  • find_json_structuresBrowse and filter every JSON Structure 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.
All 92 tools →

Call it yourself

curl for this page
This JSON Structure
curl "https://apis.io/api/v1/json-structures/problems-webhook-notification-config-structure"
All json structure
curl "https://apis.io/api/v1/json-structures?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.