More context/details in Custom API Notifications

Avatar
Ryan Clark

When utilizing Custom API notifications, the API post is fairly limited, see live example below. So if you are alerting on a “createsessionhost” it doesn't include any hostpool details? So what if there are 10 hostpools, you don't know which one…

In addition to more context from the task output, having Subject and Body included int he API notification would be extremely beneficial to users of htis feature because currently, the subject and body only apply to Emails.


{

  "AccountId": 1,

  "ActionId": 5,

  "ConditionId": 10,

  "Job": {

    "Id": 67351,

    "AccountId": 1,

    "CreationDateUtc": "2026-05-26T13:35:21.3835604+00:00",

    "JobType": "CreateSessionHost",

    "JobStatus": "Completed",

    "JobRunMode": "Default",

    "User": "user@domain.com"

  },

  "Reservations": null,

  "Usage": null,

  "BackupJob": null,

  "IntuneDeviceStatuses": null,

  "DefenderForEndpoint": null,

  "AdUserManagement": null,

  "SoftwareUpdate": null,

  "RiskyUsers": null,

  "SecureScore": null,

  "FileShareCapacity": null,

  "PolicyManagement": null,

  "CapacityExtender": null,

  "LicenseExpiration": null,

  "EmergencyAccountSignIn": null

}

3

Comments (1 comment)

Sort by
1
Avatar
Ivan de Mes

I think it would make sense to translate everything with an “id” to its actual real name or value or add it the list in addition to the “id” to prevent having to correlate across systems. For example:

“AccountId” -→ “Account Name”

Additionally it would make sense to include tenantId/subscriptionId/tenantName/subscriptionName where applicable.

A direct “deep link" to the portal/resource/job/etc. included in the output helps pointing directly to the item, alert, or anything else useful.

In general I think the request is:

Include the complete task JSON that is available in the Tasks section of NMM as part of the Custom API notification payload. ;-)

Please sign in to leave a comment.