Introduction
The Driving API exposes recorded drive history. List drives, inspect their routes and activity, and see which universal Prospects were added during each drive.
Driving API must be enabled. All endpoints under
/v1/driving require the Driving app to be
enabled for your organization. If not enabled, endpoints return a 403 with error code
driving_not_enabled.Base URL
1https://api.v2.dealmachine.com/v1/driving
Authentication
Driving endpoints use the same Bearer token as the rest of the API:
12curl https://api.v2.dealmachine.com/v1/driving/drives \ -H "Authorization: Bearer dm_sk_live_xxx"
Both Driving Endpoints are read-only.
Resources
| Resource | Description |
| List drives | List recorded drives with driver, timing, distance, and prospect counts |
| Get drive | Read a drive route, events, visits, and linked Prospects |
| Prospects | Filter with source=driving, then manage lifecycle, notes, and tags through the Prospects API |
Resource Hierarchy
12/v1/driving/drives /v1/driving/drives/{id}
Drive IDs identify where the history came from. Mobile sessions look like
drive_session_501; web routes look like drive_route_7.Prospect linkage
The drive detail response includes a
prospects array. Each item links the drive event to the current universal Prospect with prospect_id and record_id. Use /v1/prospects/{id}/notes and /v1/prospects/{id}/tags for notes and tags.Common Error Codes
| Code | Status | Description |
driving_not_enabled | 403 | Driving is not enabled for the organization |
driving_drive_not_found | 404 | Drive does not exist or is not available to the organization |