Handover

Groups the given Zásilkovna shipments into a handover batch ("Shipment" in Zásilkovna terms) and returns its barcode. The Zásilkovna courier scans this single Code 128 barcode at pickup instead of scanning every packet, so print it on your handover sheet together with the returned list of shipments.

Which shipments can be included. All shipments must belong to your account, be carried by Zásilkovna and already have a Zásilkovna packet number (they must be exported to the carrier). A shipment of another carrier or a shipment without a packet number fails the whole request with 400, a shipment that does not exist or does not belong to you fails it with 404; the errors list names the offending tracking numbers.

Repeated calls. Every shipment remembers the batch it was added to. Calling the endpoint again with the same shipments returns the same barcode without contacting Zásilkovna. When you add new shipments to an already created batch, only the new shipments form a new batch, so the response may contain several batches and the courier scans one code per batch. Shipments handed over through different Zásilkovna accounts (for example CZ and SK) always form separate batches.

Rejected packets. Zásilkovna refuses to add a packet that was already physically handed over or that is a return. Such shipments do not fail the request: they are listed in rejectedShipments and the batch is created for the remaining ones. A batch is not created at all when no packet is left.

Output format. The format field of the request body selects the response: PDF (default) returns a printable A4 handover sheet (application/pdf, sent as an attachment) with one page per batch showing the barcode in the middle, its text, the carrier batch ID and the table of shipments, followed by a page listing rejected shipments when there are any. JSON returns the batches with the barcode data and the list of shipments so you can print your own handover sheet. The batch is created and remembered the same way in both formats. Error responses are always JSON.

Rate limit. At most 10 requests per 60 seconds per account. The current state is returned in the X-Rate-Limit-Limit, X-Rate-Limit-Remaining and X-Rate-Limit-Reset response headers; exceeding the limit returns 429.