The Italian version constitutes the only official and legally binding version of the document. The English-language version of this document is provided solely as a courtesy to facilitate consultation by users. In the event of any discrepancies, interpretive differences, or inconsistencies between the Italian-language version and any translated version, the Italian text alone shall prevail and be deemed authoritative.

Send a traditional message

What are traditional messages?

When using the traditional message delivery method, the sending organization defines the message content, stores it in IO's systems, and sends it to the recipient.

When the user opens the message in IO, the previously stored information is retrieved by the back end and transmitted to the app.

How does sending a traditional message work?

Message delivery phase

Your systems integrated with IO can request the creation—and therefore the delivery—of a new message to a specific recipient. For more information about sending a message through IO, refer to ..

The following table summarizes the components of an IO message and indicates whether they are mandatory or optional:

Component	Notes	Mandatory	Remotely retrievable?
title (subject)	This is the title displayed in the message list and in the message details after it is opened. It must be between 10 and 120 characters long.
body (markdown)	This is the message's text content. It must be between 80 and 10,000 characters long.
due date (due_date)	Allows you to associate a reminder with the message. The date must use the ISO 8601 format and the UTC time zone.
payment notice (payment_data)	Allows you to include a payment notice in the message, which can be paid directly in the app. To do so, you must request the specific authorization.

When you submit the message delivery request through the dedicated endpoint, the server response will contain the message identifier. You can use it together with the recipient's Fiscal Code to check the message delivery outcome.

If you have signed the Premium agreement, you will also be able to check the recipient's read and payment status. For more information, see the Services manual.

Remember that before sending a message, you must verify that the citizen is registered with IO and that the service is authorized to send communications to them. For more information, see the API.

Message access phase

When the recipient opens the message, the app checks the information required to retrieve the message from IO's systems.

Note on forwarding messages by email

IO users can enable email forwarding for messages in the app preferences. When this option is enabled, a message sent through IO is also forwarded to the recipient's email address.

The email contains the opening portion of the message body—the first 134 characters—as well as an invitation to open the app to access the full content through a button that redirects the user.

Here is an example of a forwarded email: