Getting your bearings…
Haulage & delivery for marketplaces
PechMove is PECH’s logistics product. PMap is the map, address, GPS, and proof layer it already uses. Ecommerce and marketplaces call /api/v1 from your server for pins, tracking, and POD — and keep orders, quotes, and money in PechMove (or your own fleet). Attribution is always © PMap.
Split of responsibility
PMap — geocode, reverse, pin confirm, route, track, POD metadata, disputes, traffic where probes exist.
PechMove — haulage quotes, driver assign, rate cards, outdoor pin gates. Not hosted in this map API.
PechPay — payments (separate product).
Ecommerce → delivery flow
Suggest / reverse the pin, then POST /v1/stops/confirm. Only then is pinConfirmed true — never invent a landmark.
Create the haulage job in PechMove (or your fleet) with the confirmed lat/lng and your orderId. Quotes and drivers stay in PechMove.
Driver POST /v1/track/ping. Buyer and ops GET /v1/track/{device}?trail=1. Empty trail until a real ping — no fake GPS.
POST /v1/pod (you host the photo). POST /v1/disputes for evidence. Trip survey → /v1/integrations/pech-move/trip-outcome.
What you can access on /api/v1
Checkout pins
Route & cards
Tracking & fleet
POD & disputes
pm_live_ for production pins and GPS. pm_test_ is canned Lagos — not outdoor QA.pech-move. Your shop can use its own slug on POD / disputes.Full written guide: Logistics docs · Shareable markdown in the repo: docs/INTEGRATE-PECHMOVE.md