Create a new transport draft. Transport drafts are used to compose and validate transports before being submitted to create orders, shipments, and / or tours.

transport shape (for product evaluation). The draft's transport field is stored leniently — drafts are work-in-progress and partial shapes are accepted. However, the draft only becomes usable for POST /products/{productId}/execute once transport parses cleanly against TransportForProducts. If you intend to evaluate a product against the draft, send a transport with these top-level keys: template, shipperId, shipperTeamId, shipperUserId, order, shipments (array), sharedShipment, tour, multiStopData, discoveredFields, confirmedSections, features, properties (with shipmentsCreator and tourBar sub-objects). Any missing or malformed top-level field surfaces from /execute as HTTP 412 with the literal TransportForProductsSchema parse failed: <serialised validation issues> so you can patch the draft and retry. Optional fields under the same root: products, productsMode (defaults to "booking"), shipperOffers, smartInsights. Country codes inside customer (and similar address sub-objects) MUST be ISO-3166 alpha-3 ("DEU", not "DE").

Set recurringSchedule to create a recurring-master draft — at least 2 stops and a vehicleClassId are then required, and startsAt (if given) must not be in the past. The draft is created with status draft; activate it via POST /drafts/{id}/actions with type=activate-recurring. Omit recurringSchedule for a regular one-off draft.