What events trigger Applivery webhooks for Device Management?

Webhooks are triggered by new enrollment tokens, successful device enrollments, device employee assignments, changes and removals, Apple Push Certificate nearing expiration, and new inventory items.

How do I configure a webhook in Applivery?

In Workspace Settings, go to Integrations, create a new integration, select Webhook, enter the URL, select events, and save.

How can I identify the type of event in an Applivery webhook payload?

Use the `action` field in the JSON payload to identify the event type.

What does the `numDays` field mean in the `apple_push_certification_renovation` webhook?

The `numDays` field indicates the number of days remaining before the Apple Push Certificate expires.

What does the `enrollmentToken.type` field indicate in the enrollment token webhook?

The `enrollmentToken.type` field indicates the management mode, such as `Fully Managed`, `Work Profile`, or `Fully Managed with Work Profile` (COPE).

What does the `subAction` field indicate in the InventoryItem webhook?

The `subAction` field specifies the operation performed on the inventory item, such as `created`, `updated`, or `deleted`.

Applivery Webhooks: Real-Time Device Management Events

Q: Where are Applivery webhooks configured?

Webhook integrations are configured at the Workspace level in Applivery.

Q: What is the format of Applivery webhook payloads?

Applivery webhook notifications are delivered as HTTP POST requests with a JSON body.

Integrate Applivery with external services using custom webhooks to receive real-time notifications about key Device Management events.

Webhooks allow you to connect Applivery to any external service that accepts HTTP POST requests — ITSM platforms, custom dashboards, automation tools, and more. When a relevant event occurs in Applivery, a JSON payload is sent automatically to the URL you configure.

For Device Management, the following events can trigger a webhook notification:

A new Enrollment Token has been created.
A new Device has been successfully enrolled.
A Device Employee has been assigned to or changed on a Device.
A Device Employee has been removed from a Device.
The Apple Push Certificate is about to expire.
A new Inventory item has been registered.

Getting started

Webhook integrations can be configured at the Workspace level, so notifications from all Devices and enrollment activity within your organization are sent to the configured URL.

Navigate to Integrations

Once in the Applivery Dashboard, go to your Workspace Settings 1 from the top dropdown menu, then open Integrations 2 in the left-hand menu and click the + Create integration 3 button.

Configure the Webhook

Select Webhook as the integration type.
Enter the URL that should receive the webhook payloads.
Select the events you want to subscribe to from the list.
Click Save.

Managing Webhook Integrations

After saving, you will be redirected to the Integrations section, where your new webhook is listed with a summary of its configuration:

Type: Webhook.
Configuration: The destination URL.
Events: The list of subscribed events.

Editing a Webhook

Just click on an existing webhook integration. A side panel will open where you can update the destination URL and the subscribed events.

Deleting a Webhook

Open the webhook integration and click the Delete button in the side panel.

Event Payloads

All webhook notifications are delivered as HTTP POST requests with a JSON body. Use the action field to identify the event type and route your processing logic accordingly.

The {os} prefix in action names is replaced at runtime by the platform identifier: emm for Android, adm for Apple, win for Windows, and aos for AOSP. Android is the exception for two events (Enrollment tokens and enrolled Devices), so check the Event Reference table for the exact action name on each platform.

{
  "action": "enrollment_token_created",
  "sendEmail": true,
  "enrollmentToken": {
    "type": "Fully Managed"
  },
  "mdmUser": {
    "id": "5e9099ee4da32b180204770e",
    "email": "[email protected]",
    "url": "https://dashboard.applivery.io/test/devices/users#search=5e9099ee4da32b180204770e"
  },
  "organization": {
    "id": "5d4d1391cd523c15f50df235",
    "name": "Applivery Test",
    "url": "https://dashboard.applivery.io/test"
  }
}

Note

The enrollmentToken.type field indicates the management mode — for example, Fully Managed, Work Profile, or Fully Managed with Work Profile (COPE).

Android

{
  "action": "emm_device_created",
  "organization": {
    "id": "5d4d1391cd523c15f50df235",
    "name": "Applivery Test",
    "url": "https://dashboard.applivery.io/test"
  },
  "emmDevice": {
    "type": "Fully Managed",
    "brand": "samsung",
    "model": "SM-A536B",
    "url": "https://dashboard.applivery.io/test/devices/android~5f634c11034824062256e38c"
  },
  "mdmUser": {
    "id": "5e9099ee4da32b180204770e",
    "email": "[email protected]",
    "url": "https://dashboard.applivery.io/test/devices/users#search=5e9099ee4da32b180204770e"
  }
}

Apple

{
  "action": "adm_device_enrolled",
  "organization": {
    "id": "5d4d1391cd523c15f50df235",
    "name": "Applivery Test",
    "url": "https://dashboard.applivery.io/test"
  },
  "admDevice": {
    "productName": "iPhone15,2",
    "url": "https://dashboard.applivery.io/test/devices/apple~6650a1f2c3d4e5f6a7b8c9d1"
  },
  "mdmUser": {
    "id": "5e9099ee4da32b180204770e",
    "email": "[email protected]",
    "url": "https://dashboard.applivery.io/test/devices/users#search=5e9099ee4da32b180204770e"
  }
}

Note

The Device url follows the format /<slug>/devices/<platform>~<deviceId>, where <platform> is android, apple, or windows. For AOSP Devices, the url points to /<slug>/devices.
On Apple Devices, productName is the model identifier reported by the Device — for example, iPhone15,2 or Mac14,2.
On Apple Devices, the mdmUser object isn't included if the Device is enrolled without a user — for example, through Automated Device Enrollment with no user assigned.

Windows

{
  "action": "win_device_added_mdm_user",
  "organization": {
    "id": "5c34ec7810399b6cc062a04a",
    "name": "Applivery Test",
    "url": "https://dashboard.applivery.io/test"
  },
  "winDevice": {
    "productName": "",
    "url": "https://dashboard.applivery.io/test/devices/windows~66d05845114a9509d18e7266"
  },
  "mdmUser": {
    "id": "65f83a5e4ecbfd693b7486d6",
    "email": "[email protected]",
    "url": "https://dashboard.applivery.io/test/devices/users#search=65f83a5e4ecbfd693b7486d6"
  },
  "trigger": "deviceUpdate"
}

Apple

{
  "action": "adm_device_added_mdm_user",
  "organization": {
    "id": "5d4d1391cd523c15f50df235",
    "name": "Applivery Test",
    "url": "https://dashboard.applivery.io/test"
  },
  "admDevice": {
    "productName": "iPhone15,2",
    "url": "https://dashboard.applivery.io/test/devices/apple~6650a1f2c3d4e5f6a7b8c9d1"
  },
  "mdmUser": {
    "id": "5e9099ee4da32b180204770e",
    "email": "[email protected]",
    "url": "https://dashboard.applivery.io/test/devices/users#search=5e9099ee4da32b180204770e"
  },
  "trigger": "deviceUpdate"
}

Note

The trigger field indicates what caused the change. Check the Trigger values table for all possible values.

Android

{
  "action": "emm_device_removed_mdm_user",
  "organization": {
    "id": "5d4d1391cd523c15f50df235",
    "name": "Applivery Test",
    "url": "https://dashboard.applivery.io/test"
  },
  "emmDevice": {
    "brand": "samsung",
    "model": "SM-A536B",
    "url": "https://dashboard.applivery.io/test/devices/android~6650a1f2c3d4e5f6a7b8c9d0"
  },
  "mdmUser": {
    "url": "https://dashboard.applivery.io/test/devices/users"
  },
  "trigger": "deviceRemoval"
}

Note

On Android, Windows, and AOSP, the mdmUser object only includes the url field, without id or email.
On Windows, the Device object is winDevice, with productName and url.
On AOSP, the Device object is aosDevice, with displayName and url. Here, url points to /<slug>/devices instead of a specific Device.
On Apple, the body is the same as in adm_device_added_mdm_user, but without the mdmUser object.

{
  "action": "apple_push_certification_renovation",
  "organization": {
    "id": "5d4d1391cd523c15f50df235",
    "name": "Applivery Test",
    "url": "https://dashboard.applivery.io/test"
  },
  "numDays": "5",
  "appleId": "[email protected]"
}

Note

The numDays field indicates how many days remain before the certificate expires. The appleId field identifies the Apple ID used to create the certificate.

{
  "action": "A new InventoryItem is being registered",
  "subAction": "created",
  "organization": {
    "id": "5d4d1391cd523c15f50df235",
    "name": "Applivery Test",
    "url": "https://dashboard.applivery.io/test"
  },
  "inventoryItem": {
    "id": "62bd71d980df8b001b085ceb",
    "type": "monitor",
    "members": {
      "type": "mdmUser",
      "memberId": "6241d3d804e388001b3c605c",
      "email": "[email protected]"
    },
    "metadata": {}
  }
}

Note

Use the subAction field to determine the specific operation performed on the inventory item — for example, created, updated, or deleted.

Event Reference

Action	Trigger
`{os}_enrollment-token_created` Android: `enrollment_token_created`	A new MDM Enrollment token has been created.
`{os}_device_enrolled` Android: `emm_device_created`	A Device has been successfully enrolled.
`{os}_device_added_mdm_user`	An MDM user has been assigned to or changed on a Device.
`{os}_device_removed_mdm_user`	An MDM user has been removed from a Device.
`apple_push_certification_renovation`	The Apple Push Certificate is approaching expiration.
`A new InventoryItem {action}`	An item has been registered or updated in Inventory.

Trigger values

The trigger field in {os}_device_added_mdm_user and {os}_device_removed_mdm_user events tells you what caused the change:

Value	When it's sent
`enrollment`	The user is assigned during enrollment.
`deviceUpdate`	An administrator changes the Device's user.
`deviceRemoval`	The user is removed because the Device has been deleted.
`scim`	The change comes from SCIM directory synchronization.

Key Takeaways

Webhooks enable real-time notifications from Applivery to external services.

Applivery webhooks support various device management events.

Webhook integrations are configured at the workspace level.

Event payloads are delivered as HTTP POST requests with a JSON body.

Proper management of Apple Push Certificates is crucial for iOS device management.