Rebook a load
Changed onCreate a new load for the shipment after its carriers were bounced or TONU'd — the TMS "Re-book load".
What happens
- A new load is created on the load's order with the same stops, in sourcing and ready for a carrier
- The shipment moves back to planning
- The original load keeps its history (a TONU'd load stays delivered for the carrier's TONU bill)
Prerequisites
- The shipment is not canceled, deleted, consolidated or a tender
- Either every load of the shipment was TONU'd (a delivered shipment included), or none is still active — each is canceled or TONU'd — the shipment is not delivered, and one load was TONU'd or it has more than one load
Request
- Base URL: https://api.mvmnt.io/v1
- URL: https://api.mvmnt.io/v1/loads/{id}/rebook
- Auth: HTTP bearer
Path parameters
Resource ID (UUID) or client key
Query parameters
Specify lookup type for faster retrieval. If omitted, defaults to looking up by ID first, then falls back to client key if not found. Use by=key when you know you're providing a client key for best performance.
Response
Load rebooked successfully
Changes
- breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - breaking
removed the required property
from the response with the status - info
media type
application/jsonwas changed to a more specific media typeapplication/problem+jsonfor the response status - info
media type
application/jsonwas changed to a more specific media typeapplication/problem+jsonfor the response status - info
media type
application/jsonwas changed to a more specific media typeapplication/problem+jsonfor the response status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the optional property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status
- breaking