Italian Postal Service

For sending telegrams via API the reference endpoint is POST /telegrammi/.

In the body of the request, the data on the:

• sender (first name, last name, full address)
• recipient(s) (first name, last name, full address)
• document
• possible additional option (delivery notice)

The reply provides the details of the requested telegram, in particular

• sender (first name, last name, full address)
• addressee(s) (first name, last name, full address)
• document specifications
• final price
• telegram id

PLEASE NOTE: The id will be useful later for obtaining information on the telegram sent.

It is also possible to save the telegram for later sending via the "autoconfirm" parameter, which in this case should be set to "false". To confirm the sending at a later time, you will need to use the PATCH endpoint /telegrammi/{id} by passing the sending id and in the body of the request the value "confirmed":true

For sending registered letters via API, the reference endpoint is POST /raccomandate/.

In the body of the request, the data on the:

• sender (first name, last name, full address)
• addressee(s) (first name, last name, full address)
• document
• possible additional option (front/back, colours, return, delivery notice)

The reply provides the details of the registered mail requested, in particular

• sender (name, surname, full address)
• addressee(s) (name, surname, full address)
• document specifications
• final price
• registered mail id

PLEASE NOTE: The id will be useful later on to obtain information on the registered mail sent and for tracking purposes.

It is also possible to save the registered letter for later sending via the "autoconfirm" parameter which, in this case, must be set to false. To confirm the sending at a later date, it will be necessary to use the PATCH endpoint /raccomandate/{id} by passing the id of the dispatch and in the body of the request the value "confirmed":true

For sending ordinary mail via API the reference endpoint is POST /ordinarie/.

In the body of the request you must specify data on:

• sender (first name, last name, full address)
• recipient(s) (first name, last name, full address)
• document
• possible additional option (front/back, colours, delivery notice)

The reply provides details on:

• sender (first name, last name, full address)
• addressee(s) (first name, last name, full address)
• document specifications
• final price
• ordinary mail id

PLEASE NOTE: The id will be useful later on to obtain information on the item sent.

It is also possible to save the ordinary mail for later dispatch via the "autoconfirm" parameter which, in this case, must be set to false. To confirm the dispatch at a later date, you will need to use the PATCH endpoint /ordinarie/{id} by passing the id of the dispatch and in the body of the request the value "confirmed":true

For sending registered mails via API the reference endpoint is POST /prioritarie/.

In the body of the request, data on the:

• sender (first name, last name, full address)
• addressee(s) (first name, last name, full address)
• document
• possible additional option (front/back, colours, delivery notice)

The reply provides details on:

• sender (first name, last name, full address)
• addressee(s) (first name, last name, full address)
• document specifications
• final price
• priority mail id

PLEASE NOTE: The id will be useful later for obtaining information on the item sent and for tracking purposes.

It is also possible to save the Priority Mail item for a later dispatch via the "autoconfirm" parameter which, in this case, must be set to false. To confirm the sending at a later date, you will need to use the PATCH /prioritarie/{id} enpoint by passing the id of the mailing and in the body of the request the value "confirmed":true

For sending registered mail smart via API, the reference endpoint is POST /raccomandate_smart/.

In the body of the request, the data on the:

• sender (first name, last name, full address)
• addressee(s) (first name, last name, full address)
• document
• possible additional options (front/back, colours, return, delivery notice, possible callback URL)

The reply provides the details of the requested registered smart mail, in particular

• sender (first name, last name, full address)
• addressee(s) (first name, last name, full address)
• document specifications
• final price
• registered mail smart id

PLEASE NOTE: The id will be useful later for obtaining information on the registered smart mail sent and for tracking.

You can also save the registered smart mail for later sending via the "autoconfirm" parameter which, in this case, must be set to false. In order to confirm the sending at a later date, it will be necessary to use the PATCH endpoint /raccomandate_smart/{id} by passing the id of the sending and in the body of the request the value "confirmed":true

For sending massive mail via API the reference endpoint is POST /posta_massiva/.

In the body of the request the data on the:

• sender (first name, last name, full address)
• recipient(s) (first name, last name, full address)
• document
• possible additional option (front/back, colours, delivery notice)

The reply provides details on:

• sender (first name, last name, full address)
• addressee(s) (first name, last name, full address)
• document specifications
• final price
• massive mail id

PLEASE NOTE: The id will be useful later for obtaining information about the mailing.

It is also possible to save the massive mail for later dispatch via the "autoconfirm" parameter which, in this case, must be set to false. To confirm the sending at a later date, you will need to use the PATCH /posta_massiva/{id} endpoint by passing the id of the mailing and in the body of the request the value "confirmed":true

Yes, it is also possible to include more than one recipient for all Italian Postal services: telegram, registered, priority and ordinary mail, registered mail smart, massive mail.

Yes, the list is available via the GET method.

Depending on the service, the reference endpoint will be:

• GET /telegrammi/ for telegrams
• GET /raccomandate/ for registered letters
• GET /prioritarie/ for priority mail
• GET /ordinarie/ for ordinary mail
• GET /raccomandate_smart/ for registered mail smart
• GET /posta_massiva/ for bulk mail

No start parameter is required.

Yes, it is possible to check previous mailings via the endpoints:

• GET /telegrammi/{id} for telegrams
• GET /raccomandate/{id} for registered letters
• GET /prioritarie/{id} for priority mail
• GET /ordinarie/{id} for ordinary mail
• GET /raccomandate_smart/{id} for smart registered mail
• GET /posta_massiva/{id} for bulk mail

In all cases, the id, which is obtained when sending the product, is required as a starting parameter.

Other parameters (if set) are optional:

• receipt (for telegrams, registered, priority and ordinary mail): a PDF is returned in the reply
• status (for all services)
• callback (ONLY for the sandbox environment and only for registered mail)

You can track individual shipments for products with tracking (registered mail, priority mail, registered mail smart) via the GET /tracking/{id} endpoint, starting with the id parameter.

The time it takes for Poste Italiane to take charge of the request varies according to the service requested:

Registered Mail: in real time
Telegram: in real time
Ordinary Mail: in real time
Priority Mail: in real time
Massive Mail: in seconds
Registered Mail Smart: in seconds

The average delivery time varies depending on the service requested:

Registered mail: 4-6 working days
Telegram: from 24 hours
Ordinary Mail: from 4 days
Priority Mail: from 24 hours
Massive Mail: from 7-9 days
Registered mail Smart: from 4-7 days

The cost of a single request varies depending on the endpoint and is as low as 0,32€.

For Registered Mail: the cost starts at 4,24€.
For Telegram: the outbound cost is 3,63€.
For Ordinary Mail (Post 4): the departure cost is 1,03€.
For Priority Mail: the outbound cost is 2,28€.
Per Massive Mail: the outbound cost is 0,32€.
For Registered Mail Smart: the departure cost is 2,60€.

All prices are available in the "Pricing" section.

You can also obtain price details via the GET /pricing/ endpoint.

In the Usage section, at the API level, you can monitor your free and top-up requests. They are available both in graphical mode (period month and year) and with a textual summary.