Create and amend an ocean or truckload freight booking request using the Flexport Booking API
domain: developers.flexport.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm that parties (shipper, consignee, forwarder) and locations are already configured in your Flexport network before calling the Booking API, since bookings reference existing network identifiers rather than accepting free-form party data.
Submit an HTTP POST to the bookings endpoint with cargo, routing, and party details to create a booking (load tender) request.
Handle the synchronous response: Flexport replies with either a positive acknowledgment (HTTP 200) or a negative acknowledgment (HTTP 400) explaining why the booking request was rejected.
Use the GET bookings and GET bookings/{id} endpoints to list bookings or retrieve a specific booking's status after submission.
Use the booking amendments endpoint to modify an existing booking rather than creating a duplicate booking when cargo or routing details change.
Manage individual cargo lines via the booking line items endpoints when a booking covers multiple line items.
Known gotchas
An HTTP 400 response means the booking was rejected outright, not queued for retry — you must fix the payload and resubmit rather than expecting Flexport to reprocess it.
A booking call referencing a party or location ID that hasn't been set up in your Flexport network first will fail validation, even if the rest of the payload is correct.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?