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?

By sending traditional messages, the sending institution defines the content of the message, enters it in the IO systems and sends it to the recipient user.

When the user opens the message on IO, the information that was previously stored is retrieved by the back-end and sent to the app.

How is a traditional message sent?

Message sending phase

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

The following table summarizes the components of an IO message, specifying if they are mandatory or optional:

Component	Notes	Mandatory	Can be remote?
Subject	This is the visible subject on the list of messages and in the details (after it is opened). The length must be between 10 and 120 characters.
body (markdown)	This is the text content of the message. The length must be between 80 and 10,000 characters.
due date	This allows associating a reminder with the message. The format must be ISO-8601 with the UTC time zone.
payment notice (payment_data)	Allows sending a payment notice in the message, payable directly in app. To do so, you must request specific authorization.

When you send the request to send the message through the [specific endpoint](../../api-and-specifications/api-messages/submit-a-message-passing-the-user-tax-code-in-the-request-body.md), you will receive the response of the server that contains the message identifier. You can use it together with the fiscal code of the recipient to **check the result of sending the** message.

If you signed the Premium agreement, you can also know the **reading** **and payment** status of the recipients. For more information, consult the page [Send messages](https://app.gitbook.com/s/xWONfJmawghGo2ekuaKh/che-cosa-puo-fare-un-servizio-su-io/inviare-messaggi "mention") in the [Service manual](https://app.gitbook.com/o/KXYtsf32WSKm6ga638R3/s/xWONfJmawghGo2ekuaKh/).

Remember that before sending a message, you must check that the citizen is registered with IO and that the service can send communications to the citizen. For more information, discover the API [get-a-user-profile-using-post.md](../../api-and-specifications/api-messages/get-a-user-profile-using-post.md "mention").

Message usage phase

When the recipient citizen opens the message, the app checks the information necessary for retrieving the message in the IO systems.

Note about message forwarding via email

IO users can activate message forwarding via email in the app preferences. In this way, a message sent via IO will be forwarded also to the recipient's email address.

The email contains the incipit of the body of the message (the first 134 characters), as well as an invitation to open the app to access the complete content via a button that which permits the redirect.

Here is an example of a forwarding email: