This method allows your system to create jobs in the Last-Mile Delivery Software. This means that the order is going to be sent for fulfillment to the picking/delivery app, it's going to be tracked on the LiveOps app, all the progress is going to be shown to users in the live status widget, and you will be able to track and operate jobs through this API.

Common scenario:

Once a client confirms the purchase of an order, you will want that order to be fulfilled.

Optional fields:

• The contact_less object is used to create contactless orders in which the delivery driver does not physically interact with the client. The comment field inside this object should be one of LeaveInReception or LeaveAtTheDoor for full compatibility with our back office, but do note that these fields can be modified from the live status widget.
• The job_comment field can be used to capture any general order comments by the client. Keep in mind that this field can be modified from the live status widget.
• The add_delivery_code field can be used for security purposes and to lower fraud. If set to true, the driver will have to input a delivery code shown to the client in the live status widget (and sent in the webhooks) in order to complete the final step of the job.

Recommendations

• Consume this from your backend and expose the information through your mobile/web API.
• Associate the jobId with your order.
• Make sure that the user completes the purchase before time expires. Otherwise, the Delivery Engine will respond with a 417 status code (Expectation Failed), and the client will need to select a new delivery slot.
• Change in items, origin, or destination should trigger a new request for availability. If not, we can't guarantee the fulfillment of the job.