Skip to main content
The Driving API exposes the core Driving workspace through public API endpoints. Use it to assign driving work, save target properties, manage property tags, list tagged properties, and capture notes from the field.
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

Authentication

Driving endpoints use the same Bearer token as the rest of the API:
Driving writes require an API key that was created by a DealMachine user. That user is recorded as the creator for targets, tags, notes, and assignments.

Resources

Resource Hierarchy

Common Error Codes