Endpoint: POST /inbound-slot

Full URL: https://api.spreetaileu.com/api/api/v1/inbound-slot

Book a delivery slot before the purchase order exists. The fulfilment centre confirms the slot or proposes a different time.

Requirements

• Authentication: Bearer token required (Get token from /auth/login)

Scheduling Rules

• date must not be in the past
• Mondays are not available, except at selected Monday-accepting warehouses — your Account Manager can confirm whether yours does
• window: morning = 09:00 UK, afternoon = 13:00 UK
• containerSize is required when deliveryType is container

The slot declares the shape of the delivery

Warehouse, date, window, truck-vs-container, container size, loading type, SKU bucket and pallet count are declared here, once — the PO created from this slot inherits them, so you never send them twice. deliveryType and loadingType are optional here but strongly recommended, since leaving them out means POST /inbound-po has to ask for them.

containerTruckNumber (container number / truck registration, ≤100 chars) is optional and helps the warehouse match the booking to the shipment. A container number is usually known at booking; a truck plate often isn't — send it later on POST /inbound-po instead, or to correct this one.

What happens next

The slot starts in scheduleStatus: pending_ops. Warehouse approval is asynchronous — poll GET /inbound-slot/{slotReference}:

• confirmed: consume the slot with POST /inbound-po
• pending_customer: the warehouse proposed a different time — answer via the respond endpoint