Authenticate to the Maersk Developer Portal and subscribe your application to the Point-to-Point Schedules and Ocean Booking (DCSA) products.
Query the Point-to-Point Schedules API with origin and destination port UN/LOCODEs and a date window; parse the returned sailings for vessel name, voyage number, ETD, ETA, and transit time.
Select a sailing and submit a booking request to the Ocean Booking v2 DCSA endpoint; include commodity, container type (e.g., 20GP, 40HC), cargo weight, and the selected vessel/voyage reference.
Poll the Booking Status API with the booking reference returned in the submission response; status transitions from RECEIVED to CONFIRMED (or DECLINED) as Maersk processes the request.
On CONFIRMED status, retrieve the booking confirmation document; it contains the final vessel, voyage, port cut-off dates, and documentation deadline.
Submit shipping instructions (SI) before the SI cut-off date using the Maersk Shipping Instructions API to provide shipper/consignee details and cargo description for bill of lading generation.
Known gotchas
The Maersk Ocean Booking API implements the DCSA booking standard; field names follow DCSA conventions rather than Maersk-proprietary names — consult the DCSA specification alongside Maersk docs.
Port cut-off dates returned in the booking confirmation are critical; missing the VGM, cargo, or documentation cut-off will result in cargo rolling to the next sailing with no automatic rebooking.
Consumer Keys from the Developer Portal have rate limits; high-frequency schedule polling should use caching and respect the Retry-After header on 429 responses.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp