Proof of Visit
API-Ready GPS-verified visit detection. Structured visit records (arrival/departure, dwell, coordinates, trip ID) via REST API with optional webhook push — for field service and delivery verification.
Proof of Visit
API-Ready GPS-verified visit detection for field employees and delivery workflows. The Telematics SDK detects arrival, dwell, and departure at registered locations of interest; every visit is delivered as a structured record via REST API with optional webhook push.
Overview
Proof of Visit confirms that a driver or field employee was physically present at an assigned location — without manual check-ins, QR codes, or separate geofence apps. Visit detection runs passively through the SDK's continuous location tracking while trips are active.
Common use cases:
- Field service — verify technician arrival, dwell time on site, and SLA compliance
- Delivery — confirm stop completion and time at the delivery location
- Sales territories — objective coverage data for retail and client visits
- Inspections & audits — GPS-backed evidence that a site visit occurred
See the Proof of Visit product page for workflow examples and industry scenarios.
How it works
- Register locations of interest — define GPS coordinates (stores, client sites, job locations, facilities) through the API, each with a configurable radius
- SDK detects visits — while tracking is active, the SDK automatically detects arrival, dwell time, and departure at every registered location
- Receive structured records — each visit is delivered through the REST API as a structured record, with optional webhook push to your backend
No manual action is required from the driver beyond normal SDK tracking.
Visit record fields
Each detected visit includes:
| Field | Description |
|---|---|
| Location ID | Identifier for the registered location of interest |
| Arrival timestamp | When the driver entered the location radius |
| Departure timestamp | When the driver left the location radius |
| Dwell duration | Time spent at the location between arrival and departure |
| GPS coordinates | Verified position at the visit location |
| Trip ID | Associated trip the visit occurred within |
Use visit records to match against assigned routes, compare actual vs. planned schedules, and flag missed or shortened stops in your CRM, ERP, or field-management platform.
API delivery
Proof of Visit is API-Ready:
- REST API — query and retrieve structured visit records programmatically
- Optional webhook push — receive visit events on your infrastructure as they occur
To receive webhook callbacks, configure Backend notifications (AWS SNS, Azure Service Bus, or Azure Event Grid) at portal.damoov.com/callbacks. The same notification infrastructure used for trips and crash events applies to visit delivery.
Related pages
Updated about 1 hour ago