Dealertrack DMS is dealership management software from Cox Automotive that runs core store operations: vehicle inventory, desking and F&I, service and parts, and accounting. An unofficial API lets you pull vehicles, customers, deals, repair orders, parts, and GL data—and push new deal

Dealertrack DMS is a cloud-based dealer management system used by automotive retailers to run sales, F&I, service/parts, and back-office financials. It centralizes vehicle inventory, customer and deal workflows, repair orders, parts inventory, and the general ledger across one or many rooftops.
Core product areas include:
Common data entities:
Dealers live in Dealertrack DMS, but automating portal-first workflows is non-trivial:
Supergood reverse-engineers authenticated browser flows and network interactions to deliver a resilient API endpoint layer for your Dealertrack tenant(s).
Book a 30-minute session to confirm your modules, licensing, and authentication model.
We deliver a hardened Dealertrack DMS adapter tailored to your workflows and entitlements.
Go live with continuous monitoring and automatic adjustments as Dealertrack evolves.
- Mirror vehicles (new/used, in-transit) into your platform with pricing, photos, and options - Power pricing optimization, photo overlays, and VDP content without manual exports - Keep stock changes consistent across websites, classifieds, and inventory tools
- Create deals from online checkouts or lead flows with taxes/fees, trades, and protection products - Push lender preferences, capture decisions, and update deal status programmatically - Generate compliant buyer’s orders and attach documents back to the DMS
- Ingest open/closed ROs with labor ops, parts lines, and advisor/tech assignments - Trigger follow-ups on declined services and drive marketing automations - Sync service appointments and capacity into your scheduling product
- Post journal entries from your financing/payment rails into the DMS GL - Reconcile deals and ROs against your ERP with consistent mappings - Feed a data warehouse with normalized, multi-store metrics
Authentication
Username/password with MFA (SMS, email, TOTP) and SSO/OAuth where enabled; supports service accounts or customer-managed credentials
Response format
JSON with consistent resource schemas and pagination across modules
Rate limits
Tuned for enterprise throughput while honoring dealer entitlements and usage controls
Session management
Automatic reauth and cookie/session rotation with health checks
Data freshness
Near real-time retrieval of inventory, deals, ROs, and accounting objects
Security
Encrypted transport, scoped tokens, and audit logging; respects Dealertrack role-based permissions and rooftop scoping
Webhooks
Optional asynchronous delivery for long-running workflows (e.g., lender decisions, RO status changes, period close)
Latency
Sub-second responses for list/detail queries under normal load
Throughput
Designed for high-volume inventory sync and deal/RO processing across multi-store groups
Reliability
Retry logic, backoff, and idempotency keys minimize duplicate actions and respect posting rules
Adaptation
Continuous monitoring for UI/API changes with rapid adapter updates
Supergood supports workflows across commonly used modules such as Sales & F&I (deals, lender selections), Inventory (vehicles, pricing), Service (repair orders, appointments), Parts (lines, pricing), and Accounting (GL accounts, journal entries), subject to your licensing and entitlements.
We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. Sessions are refreshed automatically with secure challenge handling and session rotation.
Yes. We can create and update deals with figures, trades, products, and lender preferences, attach documents, and track lender decisions—while respecting permissions and posting rules.
Yes. We scope data by rooftop and department, align with store-level entitlements, and provide normalized identifiers to simplify group-wide reporting.
We detect period states, prevent out-of-period posts, enforce balanced entries, and log idempotent request keys and user/session attribution for auditing.