AsyncAPI channel · Butlr
· Butlr Real-Time Occupancy Webhooks
{subscriberWebhookUrl}
The subscriber-hosted HTTPS endpoint Butlr POSTs events to.
Channel address
{subscriberWebhookUrl}
Parameters
subscriberWebhookUrl— The webhook URL registered by the subscriber via the GraphQL API.
Operations
receive
receiveOccupancyEvents
Receive real-time occupancy, traffic, detection, and motion events.
Messages
DETECTIONS
Coordinates (x,y) of detected people within a sensor's field of view.
Content-Type:
TRAFFIC
Someone enters or exits a monitored area.
Content-Type:
FLOOR_OCCUPANCY
Number of occupants on a floor (also FLOOR_OCCUPANCY_1MIN, 1-minute smoothed).
Content-Type:
ROOM_OCCUPANCY
Number of occupants in a room (also ROOM_OCCUPANCY_1MIN, 1-minute smoothed).
Content-Type:
ZONE_OCCUPANCY
Number of occupants in a zone (also ZONE_OCCUPANCY_1MIN, 1-minute smoothed).
Content-Type:
PIR_MOTION
PIR motion (PIR_MOTION) or no-motion (PIR_NO_MOTION) from the Heatic2+ sensor.
Content-Type:
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.