The same pricing as GET /deliveries/{id}/cost, for a group of deliveries: the items added up, the totals, and one subtotal per delivery. Give exactly one of delivery_ids, batch_id or pin. Needs deliveries.read.
Typical use, a debt collector's invoice to a debtor: list the debtor's deliveries with GET /deliveries?pin=…, pick the ones for this claim, then ask for their cost here with delivery_ids. Or pass pin to cost everything sent to that person.
Only deliveries you may see count: pin and batch_id leave the others out, and a delivery_ids entry you may not see is delivery_not_found. The totals cover the whole group; limit and cursor page the per-delivery subtotals, newest first. Query strings never reach Parasend's logs, so pin is safe here.
A period.from and to keep the items that arose in it (when the notice, reminder or eID happened, not when the delivery was created), so a monthly run counts each cost once. Both dates are inclusive, whole days in UTC; either may be left out. A bounce in the period of a delivery charged earlier is a credit line with a negative quantity, so a past period never changes and the periods add up to the whole. Only deliveries with something in the period are listed. final is true once nothing more can arise in the period and every item in it is invoiced. Example: ?pin=0101304339&from=2026-10-01&to=2026-10-31.
Every delivery to the recipient with this personal code (e.g. kennitala), exact match only; spaces and hyphens are ignored — as pin on GET /deliveries.