Whispir’s Events API allows you to capture, create, manage and track events (including incidents, issues, places and assets) that are taking place within your organisation. You can link multi-channel communications to each event to track, report and disseminate information textually and geo-spatially.

The Events module can be customised to accept events and associated information from external systems or to capture more complex information around an event.

Events can be created from within the Whispir platform through the web interface, or via the REST or WSDL APIs. This information is then available for the author to distribute templated messages, or (if location enabled) for other users to view on Whispir’s map interface.

Events within the Whispir platform are generally active for a short period, usually defined by a start date and end date. Once the event’s end date is reached the event is deemed closed.

Whispir consultants work with each customer to design and build an Events module that is specific to them. The consultants ensure that the fields, applicable values and captured information relate directly to the customer’s processes.

Examples of events: An internal system or service outage, or an organisation-wide event, such as a media launch, a network outage or an incident (bush fire, flood).

  • JSON
  • XML

API endpoint


Content-Type: application/vnd.whispir.event-v1+json


Limited to a workspace

Content-Type: application/vnd.whispir.event-v1+json


Resource type



Methods supported