BioT Notification Plugins

BioT notification plugins are called when certain actions are completed successfully. BioT is not affected by the plugin response; success or failure.

Subscribing to Events

To subscribe to an API, call the subscribe API of the service:
POST https://your-biot-domain.com/dispatcher/v1/hooks/notifications/subscribe

ParameterDescriptionFormat
entityTypeNameThe entity type that you would like to be notified about.
See the API documentation for available values.
Mandatory.
String
actionNameThe action performed on the entity that you would like to be notified about.
See the API documentation for available values.
Mandatory.
String
endpointA valid URI for the platform to call when the event is triggered.
Mandatory.
String

Notification that you can subscribe to:

EntityDescriptionAvailable Actions
usage-sessionRegular or remote usage sessions_create
_remoteStart
_remoteStop
_remotePause
_remoteResume
_list
_update
_delete
_read
generic-entityAny entity based on the generic entity template_create
_read
_update
_list
_delete
caregiverAny user based on the caregiver template_create
_read
_update
_list
_delete
_login
_logout
patientAny user based on the patient template_create
_read
_update
_list
_delete
_login
_logout
_saveMeasurement
organization-userAny user based on the organization-user template_create
_read
_update
_list
_delete
_login
_logout
organizationAny organization in the system_create
_read
_update
_list
_delete
deviceAny device in the system_create
_read
_update
_list
_delete
_generateCertificate
_revokeCertificate
_activateCertificate
commandDevice command related actions_create
_update
_start
_stop
_delete
device-alertDevice alert related actions_create
_read
_update
_list
_delete
patient-alertPatient alert related actions_create
_read
_update
_list
_delete

Unsubscribing from Events

Using the same dispatcher service, you can unsubscribe from an event.
To unsubscribe from an event, call the unsubscribe API of the service:
POST https://your-biot-domain.com/dispatcher/v1/hooks/notifications/unsubscribe

The call body JSON should be the same as the subscribed call.

Unsubscribe from events call body example:

{
  "entityTypeName": "device",
  "actionName": "_create",
  "endpoint": "string"
}