Webhooks

Get a POST from MobAI when a device connects or goes away, or when its bridge starts or stops.

Overview

MobAI can tell another service when a device connects or goes away, and when the bridge on a device starts or stops. Add webhook URLs from Integrations → Webhooks in the app title bar.

Each delivery is one HTTP POST with Content-Type: application/json and User-Agent: MobAI-Webhook/1.0. Each event is sent once. A failed delivery is not retried. A request times out after 10 seconds, and any status of 400 or above counts as a failure.

You can add several webhooks, pick the events each one gets, and turn each one on or off. A webhook with no events picked gets every event.

The Test button sends one delivery with the event test and a made-up device, and shows the status code your endpoint answered with.

Events

Event When it fires
device:connected An iPhone, Android phone, simulator or emulator shows up in MobAI
device:disconnected A device that was connected is gone
bridge:started The bridge on a device started and MobAI can control it
bridge:stopped The bridge was stopped, ended by itself, or its simulator was shut down

Payload

Every delivery has the same JSON body:

{
  "event": "device:connected",
  "timestamp": "2026-11-05T10:30:00Z",
  "data": {
    "deviceId": "00008101-000A1C3E2100001E",
    "platform": "ios",
    "name": "iPhone 15 Pro"
  }
}
Field Type Description
event string One of the events above, or test from the Test button
timestamp string When it happened, in UTC (RFC 3339, whole seconds)
data.deviceId string The device's id, the same one the HTTP API uses (UDID on iOS, serial on Android)
data.platform string ios or android. Missing from bridge:stopped when the bridge ended by itself or its simulator was shut down
data.name string The device name shown in MobAI

Custom Headers

Each webhook can send its own HTTP headers with every delivery, such as an auth token or an API key your endpoint checks.

Headers are kept in the system keychain (Keychain on macOS, Credential Manager on Windows, the Secret Service keyring on Linux), not in MobAI's settings file. On a Linux machine with no keyring they go to a file only your user can read. They leave this computer only inside each delivery.