create a driver trip assigning a route of machines in vendsoft
domain: vendsoft.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with your VendSoft API key
Confirm the driver already exists in VendSoft — trips reference an existing driver by email or username, they don't create one
POST to https://secure.vendsoft.com/api/v2/trips with delivery_date (or deliveryDate), driverEmail, an optional description, and a machineCodes array listing every machine on the route
Accept the returned tripNumber and store it for tracking the trip through completion
Use one of the accepted date formats (yyyy-MM-dd, yyyy-MM-dd HH:mm:ss, or ISO 8601 with a trailing Z) for the delivery date field
Known gotchas
the trip is created in "Created" status only — this endpoint doesn't start or complete the trip
machineCodes must be a non-empty array or the request is rejected
the API accepts both snake_case (delivery_date, machine_codes) and camelCase (deliveryDate, machineCodes) field names — pick one convention and stay consistent to avoid confusing partial payloads
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?