Vehicle Inventory
/inventoryVINStock NumberYearMakeModelTrimMileageNew / UsedPricingVehicle StatusInventory AgeLocation
Data domains
Automotive Data Your Applications Need
Standardized dealership data objects — inventory, customers, sales, repair orders, appointments, parts, F&I, and employees — available through one dealership API regardless of which DMS sits underneath.
Data domains
Eight Standardized Data Domains
Customer Data
/customersCustomer IDNameContact InformationCustomer TypeVehicle OwnershipCommunication Preferences
Sales Data
/salesDeal NumberVehicleCustomerSalespersonSale DateSelling PriceGross ProfitTrade-In Information
Repair Orders
/repair-ordersRepair Order NumberVehicleCustomerService AdvisorTechnicianLabor OperationsPartsOpen DateClose DateRepair Status
Service Appointments
/appointmentsAppointment DateCustomerVehicleService AdvisorRequested ServicesAppointment Status
Parts Data
/partsPart NumberDescriptionInventory QuantityCostRetail PriceOrder Status
F&I Data
/fniDeal InformationFinance TypeLenderProduct InformationContract Status
Employee Data
/employeesSalespeopleService AdvisorsTechniciansManagersDepartment Information
Sync modes
Historical, Incremental, and Event-Driven
Get the full history when you onboard a dealership, then stay current with the sync mode that fits each data domain.
Historical Backfill
Load historical dealership records when a new store is connected.
Incremental Sync
Pull only what changed since the last successful synchronization.
Event-Driven Updates
Receive changes as webhook events when the source DMS supports it.
On-Demand Queries
Query normalized data through the API whenever your app needs it.
Sync mode availability varies by DMS provider and data domain.
Unified data model
Same Record Shape for Every DMS
Whether a repair order originates in CDK, Reynolds & Reynolds, Dealertrack, or Tekion, your application receives it in the same standardized structure — with the source DMS recorded for traceability.
- Consistent field names, types, and enumerations
- Related records linked by stable IDs (customer, vehicle, employee)
- Source system and sync timestamps on every record
repair-order.json
{
"repairOrderId": "RO-558201",
"dealerId": "DLR10234",
"vin": "1FTFW1E87PFA12345",
"customerId": "C-884120",
"serviceAdvisorId": "EMP-2207",
"technicianIds": ["EMP-3104"],
"status": "CLOSED",
"openedAt": "2026-10-03T08:12:00Z",
"closedAt": "2026-10-03T15:40:00Z",
"laborOperations": [
{ "opCode": "01FZ", "description": "Oil & filter change", "hours": 0.5 }
],
"totals": { "labor": 528.20, "parts": 84.20 },
"source": { "dms": "tekion", "syncedAt": "2026-10-03T15:41:07Z" }
}
Get started
Need DMS Data in Your Application?
Whether you're building an automotive SaaS platform, CRM, AI application, analytics platform, or dealer technology solution, AutoIntegration.io provides the integration layer between dealership systems and your product.