canonical: https://jentic.com/apis/h-mdm.com/h-mdm # H Mdm Headwind MDM Push Notifications API Jentic publishes the only available OpenAPI specification for Headwind MDM Push Notifications API, keeping it validated and agent-ready. Headwind MDM is an open-source mobile device management platform for Android fleets, and this API surface exposes a single endpoint for sending push notifications to managed devices. The endpoint accepts a notification payload and a target device list and dispatches the message via the MDM server. Authentication is via bearer token issued by the self-hosted Headwind MDM server. ## For AI agents Send push notifications to devices managed by a Headwind MDM server through one bearer-authenticated REST endpoint. ## Scope Does not handle device enrolment, app deployment, or policy configuration - use for sending push notifications to Headwind MDM-managed devices only. ## Capabilities - Send a push notification payload to a list of devices managed by a Headwind MDM server - Target notifications by device identifier, group, or configuration - Carry custom message bodies and metadata in the notification payload - Integrate with self-hosted Headwind MDM deployments via configurable base URL - Authenticate against the local MDM server using a bearer token ## Use cases ### Operational alerts to managed Android fleets Push operational alerts (downtime, password rotation, urgent policy change) to a fleet of Android devices managed by Headwind MDM. The single REST endpoint dispatches a notification payload to the requested devices via the MDM server, replacing email or SMS for fleet-wide announcements. Suitable for retail point-of-sale, logistics handhelds, and field-service tablets. Example prompt: POST `/rest/private/push` with the device list and notification payload to alert all warehouse handhelds of a system maintenance window. ### Workflow-triggered device messaging When a backend workflow detects an event - e.g., a pending field-service ticket - an automation sends a push notification to the assigned device through the Headwind MDM server. Because the API has a single endpoint, the integration is a thin call from any workflow engine into the MDM server. Example prompt: POST `/rest/private/push` with the technician's device ID and a payload containing the ticket number and address. ### Integration with on-call and incident tools Wire Headwind MDM into an on-call or incident-response tool so alerts that need to reach managed devices in addition to standard channels are dispatched on the same trigger. The API's bearer-auth model fits well with existing internal-platform automation that already manages secrets centrally. Example prompt: On a critical incident, POST `/rest/private/push` with the on-call device list and an alert payload referencing the incident ID. ### AI agent fleet ops via Jentic An AI assistant in a fleet-ops console handles a request to notify all warehouse devices of an urgent inventory recount by calling the Headwind MDM push endpoint. Through Jentic the agent loads the operation on demand instead of hard-coding the self-hosted base URL. Example prompt: Search Jentic for 'send push notification to managed devices', load POST `/rest/private/push`, and execute with the device IDs and message body. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/rest/private/push` | Send a push notification to devices | ## Key resources - **Push** — Send a push notification payload to a list of managed devices via the Headwind MDM server ## Why Jentic - **Setup:** Wiring the Headwind MDM Push Notifications API by hand means handling its bearer token, pointing every call at your own deployment-specific server host, and building the POST `/rest/private/push` request yourself. Through Jentic you install once, import the Headwind MDM Push Notifications API from the API Directory, store the token once alongside your server URL, and your agent calls it. - **Permission scoping:** This API exposes a single push operation and the target devices travel in the request body, so scope your agent to the operations it needs, such as sending a push notification. You choose what it may call, so it does no more than deliver notifications to your managed devices. - **Credential handling:** Your Headwind MDM bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send a push notification to managed devices', and Jentic returns the POST `/rest/private/push` operation with its input schema for the device list and payload so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **OneSignal** — Cloud push-notification platform for mobile, web, and email - **Pushover** — Simple push-notification API for personal and small-team alerts - **Jamf Pro** — Apple-focused MDM platform for managed iOS and macOS fleets ## FAQ ### Why is there no official OpenAPI spec for Headwind MDM Push Notifications API? Headwind MDM does not publish an OpenAPI specification for this surface. Jentic generates and maintains this spec so that AI agents and developers can call Headwind MDM Push Notifications API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Headwind MDM Push Notifications API use? Headwind MDM uses HTTP bearer authentication. Tokens are issued by the self-hosted MDM server's admin console. Through Jentic, the token is stored encrypted in the vault and only scoped tokens are passed to the executing agent. ### Can I send a notification to a specific device with the Headwind MDM API? Yes. POST `/rest/private/push` accepts a list of device identifiers in the payload alongside the notification body. To target a single device, supply a one-element device list. ### Is the Headwind MDM API self-hosted? Yes. Headwind MDM is open-source and deployed on infrastructure you control. The base URL in the spec uses {your-hmdm-server} as a placeholder - set it to your own server's URL when configuring the integration in Jentic. ### What are the rate limits for the Headwind MDM API? Rate limits depend on the deployment. Headwind MDM does not enforce a fixed cloud limit because it is self-hosted, but the underlying server hardware and FCM/APNS provider quotas determine practical throughput. Back off on 429 responses if your operator has configured rate-limiting middleware. ### How do I send a push notification through the Headwind MDM API via Jentic? Search Jentic for 'send push notification to managed devices', load the POST `/rest/private/push` operation, then execute with the device list and message payload. Install with pip install jentic. ### Can I limit what my agent is allowed to do with the Headwind MDM Push Notifications API? Yes. Jentic One is self-hosted, so you run it on your own infrastructure and your own rules decide which operations and credentials the agent may use. This API exposes a single operation, POST `/rest/private/push`, so you scope the agent to just that push call, and it can do no more than dispatch notifications to the managed devices you list in the request body. The bearer token for your Headwind MDM server stays with your instance and is injected only when a permitted call runs.