ImmobiNet API Docs - Messages
PMS ImmobiNet - Messages exchanged with guests and customers: email, SMS and Airbnb (read, and reply with drafts).
Timezone: All date-time values in this API are in the Europe/Rome timezone
(UTC+1 in winter, UTC+2 in summer). Dates follow RFC 3339 format with explicit offset,
e.g. 2026-06-26T14:30:00+02:00.
Content negotiation: this API only produces application/json. Clients must send an
Accept header that permits it (application/json, application/*, */*, or omit the
header entirely); any other Accept value is rejected with 406 Not Acceptable.
Change notifications (webhook): for every message, including drafts and outgoing messages
(not only incoming ones), the system sends a notification with event TrackMessaggi/Messaggio
and type created, modified or removed each time a message is created, modified or deleted
in a way that changes the message itself (for example its status, send time, read time or
extra data). Changes to the attachments of a draft do not raise notifications. Notifications are sent to every URL configured in the web service configuration; the optional filter on
notification types is matched against the event name TrackMessaggi/Messaggio (the type
created/modified/removed is not part of the filter, so all three are delivered together).
The call is an HTTP GET with a query string (POST is used only when a notification has a
body, which is never the case here) and carries these parameters, in this order:
id (message id), tipo (message transport: the same value as the transport field of the messages of this API, i.e. email, sms, sms-smart or airbnb), _event
(always TrackMessaggi/Messaggio), _type (created, modified or removed) and ref
(the customer code, appended on delivery). Example, for a URL configured as
https://example.com/hook:
Code
The notification does not contain the message content: the consumer must read the message
again through this API using id (not possible after removed). Notifications are sent
only after the change has been saved successfully, and identical notifications (same event,
type and parameters) close in time are delivered once.
created is sent as soon as the message is saved. When replying to an email message the body
is written right afterwards, with a subsequent modified notification: a consumer that reads
the message upon created may not find the text yet and should read it again on modified.
Notifications are best-effort: a notification that fails is lost, with no retry, and the change to the message is not affected.

