Insert a delivery order into Shipday via the REST API
domain: docs.shipday.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get an API key from the Shipday Dispatch Dashboard's Integrations tab.
POST a JSON body to https://api.shipday.com/orders with required fields: orderNumber, customerName, customerAddress, customerPhoneNumber, restaurantName, and restaurantAddress.
Optionally include pickupLatitude/pickupLongitude and deliveryLatitude/deliveryLongitude to skip Shipday's own geocoding of the address strings.
Set paymentMethod to cash or credit_card; if credit_card, also include creditCardType (VISA, MASTER_CARD, AMEX, or OTHER).
Read the response's success boolean and orderId to confirm the order was created before relying on it downstream.
Use the orderItem array (name, unitPrice, quantity, addOns) if the order should show itemized contents to the driver.
Known gotchas
expectedPickupTime and expectedDeliveryTime are UTC time-of-day values (hh:mm:ss), not local time — a common source of orders appearing scheduled for the wrong hour.
orderNumber should be unique per order; a 400 response doesn't always name a single obvious cause, so check the returned message string rather than assuming which field is invalid.
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?