HipChat Webhooks API
Event-driven webhook delivery from HipChat rooms. Webhooks could be registered via the REST API or declared in an add-on descriptor. Each delivery included a JWT-signed signed_request query parameter that the receiving service was expected to verify. The room_message event was the primary integration pattern, with additional events covering room enter, exit, topic change, archive, notification, and file upload. The webhook surface was retired with the rest of HipChat on February 15, 2019.
This event API exposes 10 operations across 10 channels, and defines 13 schemas. It is described by AsyncAPI 2.6.0, at version 2.0.
The API connects through a single server, hipchat-cloud (https).
Metadata
The identity and technical contract details declared by the specification.
Channels & Operations 10
Across 10 channels, the API surfaces 10 operations. Each is listed below with its action, channel, parameters, and response codes.
Messages & Schemas 13
The contract defines 13 schemas that model the data carried by its messages. The most detailed is BaseEnvelope (4 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable AsyncAPI contract behind this narrative.