Create an Opendock carrier account and authenticate by POSTing your credentials to the /auth/login endpoint; the response returns a JWT token, which you include as Authorization: Bearer in all subsequent requests.
Search for the target warehouse using the /carrier/warehouse-search endpoint with a search string (warehouse name, address, or organization name) to retrieve the facility's Opendock ID.
Query available appointment slots for the warehouse by calling the availability endpoint with the facility ID, desired date range, and dock type (inbound or outbound); the response returns open time slots.
Book an appointment by POSTing to the appointment creation endpoint with the warehouse ID, selected slot, load details (commodity, quantity, weight), and reference numbers (PO number, BOL); confirm any custom fields required by that facility.
Receive the appointment confirmation including a confirmation number; store this against your shipment record in your TMS or OMS to track dock schedule adherence.
Monitor for appointment changes or cancellations via the Opendock streaming events API (Subspace) or by polling the appointment status endpoint; notify drivers and update dispatch plans accordingly.
Known gotchas
Many facilities configure custom required fields (PO validation, commodity codes, equipment type) via Opendock's Appointment Validation protocol — always retrieve the facility's field requirements before attempting to book.
JWT tokens expire; implement proactive token refresh to avoid mid-session authentication failures during appointment searches or multi-step booking flows.
Appointment slots are held temporarily upon selection but not guaranteed until the booking is confirmed — complete the booking POST promptly after slot selection to avoid conflicts with other carriers.
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