The CourierPickupClosureRequest API serves as the execution trigger for Manual Bulk Pickup workflows, processing accumulated shipments in the previously created shipments batch and submitting pickup requests to courier systems. This API transforms collected shipments from the accumulation mode into active pickup requests with scheduled courier coordination.
The required fields are:
The PickupBatchID, which must be an existing batch created by the requesting MOL user in the previously created shipments
The PickupData container fields:
Date: in format YYYY-MM-DD, must be current or future date
PreferredFrom: requires a HH:MM format and it's the starting time of the preferred pickup window. Must be a valid time format and logically before PreferredTo
PreferredTo: requires a HH:MM format and it's the end time of the preferred pickup window. Must be a valid time format and logically later than PreferredTo
Alternative from: start time HH:MM format of alternative pickup window. This is a backup option if preferred window is unavailable, and should not overlap with preferred window and logically before AlternativeTo
AlternativeTo: end time HH:MM format of alternative pickup window. This is a backup option if preferred window is unavailable, and should not overlap with preferred window and logically later than AlternativeFrom
Notes: standard instructions or special requirements for pickups (e.g., Contact before arrival)
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ws="http://www.onlinembe.eu/ws/">
<soapenv:Header/>
<soapenv:Body>
<ws:CourierPickupClosureRequest>
<RequestContainer>
<System></System>
<Credentials>
<Username></Username>
<Passphrase></Passphrase>
</Credentials>
<InternalReferenceID>abcde</InternalReferenceID>
<!-- Required: Batch Identification -->
<PickupBatchId>284374324324</PickupBatchId>
<!-- Required: Pickup scheduling data -->
<PickupData>
<Notes>Warehouse loading dock - ring buzzer 3 times</Notes>
<Date>2025-07-14</Date>
<PreferredFrom>10:00</PreferredFrom>
<PreferredTo>14:00</PreferredTo>
<AlternativeFrom>15:00</AlternativeFrom>
<AlternativeTo>17:00</AlternativeTo>
</PickupData>
</RequestContainer>
</ws:CourierPickupClosureRequest>
</soapenv:Body>
</soapenv:Envelope>
The response will show a recap of the shipments that have been processed and the pdf of the pickup manifest generated from those shipments:
<ns3:CourierPickupClosureRequestResponse xmlns:ns3="http://www.onlinebe.eu/ws/">
<RequestContainer>
<InternalReferenceID>dsds</InternalReferenceID>
<Status>OK</Status>
<TotalShipmentPickups>2</TotalShipmentPickups>
<TotalPackages>2</TotalPackages>
<PickupClosureDetails>
<status>OK</status>
<ShipmentPickups>2</ShipmentPickups>
<TotalPackages>2</TotalPackages>
<ShipmentPickup>
<MBETrackingNumber>IT0001-0P-0000000037D</MBETrackingNumber>
</ShipmentPickup>
<ShipmentPickup>
<MBETrackingNumber>IT0001-0P-0000000037E</MBETrackingNumber>
</ShipmentPickup>
</PickupClosureDetails>
<Label>
<Stream>...</Stream>
<Type>PDF</Type>
</Label>
</RequestContainer>
</ns3:CourierPickupClosureRequestResponse>