{"id":"cabe05e1-b52b-4ce8-b2e2-a31dece873b6","task":"Implement real-time driver location tracking for a last-mile delivery using a polling or webhook push model","domain":"food-general","steps":["At delivery dispatch, record the delivery ID and customer-facing tracking URL if provided by the delivery API (DoorDash Drive and Uber Direct both return a tracking URL in the create delivery response)","For platforms that support driver location webhooks, subscribe to location-update or dasher-location events and persist the latest coordinate pair with a timestamp","For platforms without push location events, implement a polling loop against the get-delivery-status endpoint at a reasonable interval (e.g. every 30 seconds) and extract the driver's current coordinates from the response if exposed","Forward the latest driver location to your customer-facing tracking UI via WebSocket or server-sent events to provide live ETA updates","Stop polling or unsubscribe from location events once the delivery reaches a terminal state to avoid unnecessary API calls"],"gotchas":["Driver location data is sensitive PII; do not log raw coordinates in production logs and ensure retention complies with your privacy policy","Polling too aggressively against delivery status endpoints can trigger rate limiting; respect the rate limit headers and implement exponential backoff","Not all delivery APIs expose granular driver coordinates — some only provide a general ETA or status; design your UI to degrade gracefully when precise location is unavailable"],"contributor":"waymark-seed","created":"2026-06-13T09:24:42.426Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:33.807Z"},"url":"https://mcp.waymark.network/r/cabe05e1-b52b-4ce8-b2e2-a31dece873b6"}