Platform
Platform overview DMS AggregationData NormalizationData DeliveryIntegration MonitoringAgentic AI Engine
Integrations Data
Solutions
Solutions overview Automotive SaaSDealer GroupsAI PlatformsCRM PlatformsAnalytics PlatformsService Technology
Developers
Developers overview API OverviewDocumentationWebhooksData ModelsIntegration Status
Security Company Contact Request Demo
Developers

One API for Dealership Data Across Every DMS

A unified automotive data API with consistent resources, fields, and errors — plus webhooks, a sandbox, and standardized data models so your team never has to learn the internals of each DMS.

API-first platform

Built for Developers

AutoIntegration.io provides a developer-friendly integration layer that removes much of the complexity involved in communicating with multiple dealership systems. One dealer management system API — consistent resources, consistent fields, consistent errors.

200 OK

  
Developer experience

Designed for Integration Teams

Everything your engineers need to go from API key to production data — without learning the internals of every DMS.

  • Developer Documentation
  • API Reference
  • Sandbox Environment
  • API Keys
  • OAuth Support
  • Webhook Configuration
  • Sample Payloads
  • Postman Collections
  • SDK Possibilities
  • Integration Status Dashboard
  • Logs
  • Error Messages
  • Developer Support
quickstart.sh
# 1. List the dealerships your key is authorized for
curl https://sandbox.api.autointegration.io/dealers \
  -H "Authorization: Bearer $AI_SANDBOX_KEY"

# 2. Pull normalized inventory for one dealer
curl https://sandbox.api.autointegration.io/dealers/DLR10234/inventory?status=AVAILABLE \
  -H "Authorization: Bearer $AI_SANDBOX_KEY"

# 3. Page through results with a cursor
curl "https://sandbox.api.autointegration.io/dealers/DLR10234/repair-orders?since=2026-10-01&cursor=cur_8f2a" \
  -H "Authorization: Bearer $AI_SANDBOX_KEY"

# Same endpoints, same fields — whichever DMS the dealer uses.
Webhooks

Event-Driven Dealership Data

Subscribe once and receive standardized events from every connected dealership — regardless of the underlying DMS. Payloads are signed so your endpoint can verify they came from AutoIntegration.io.

inventory.createdinventory.updatedinventory.soldcustomer.createdcustomer.updatedrepair_order.openedrepair_order.closedappointment.createdappointment.updatedsale.completedpart.updatedconnection.status_changed

Event availability depends on the source DMS and integration method.

webhook-subscription.sh
# 1. Subscribe to repair-order events (sandbox)
curl -X POST https://sandbox.api.autointegration.io/webhooks \
  -H "Authorization: Bearer $AI_SANDBOX_KEY" \
  -d '{
    "url": "https://app.example.com/hooks/dms",
    "events": ["repair_order.closed", "inventory.updated"],
    "dealerIds": ["DLR10234", "DLR10871"]
  }'

# 2. Event delivered to your endpoint — same shape for every DMS
{
  "event": "repair_order.closed",
  "dealerId": "DLR10234",
  "sourceDms": "tekion",
  "data": {
    "repairOrderId": "RO-558201",
    "vin": "1FTFW1E87PFA12345",
    "status": "CLOSED",
    "totalAmount": 612.40
  }
}
Data models

The Standardized Automotive Schema

Every DMS is mapped into the same set of objects, so your code is written once against one dealer management system API.

ObjectEndpointKey fieldsEvents
Dealer/dealersdealerId, name, dms, status, lastSyncAtconnection.status_changed
Vehicle/dealers/{dealerId}/inventoryvin, stockNumber, year, make, model, trim, mileage, inventoryType, statusinventory.*
Customer/dealers/{dealerId}/customerscustomerId, name, contact, customerType, ownedVehicles, preferencescustomer.*
Sale/dealers/{dealerId}/salesdealNumber, vin, customerId, salesperson, soldAt, sellingPrice, grossProfit, tradeInsale.completed
Repair Order/dealers/{dealerId}/repair-ordersrepairOrderId, vin, customerId, serviceAdvisor, technician, laborOperations, parts, statusrepair_order.*
Appointment/dealers/{dealerId}/appointmentsappointmentId, scheduledAt, customerId, vin, requestedServices, statusappointment.*
Part/dealers/{dealerId}/partspartNumber, description, quantityOnHand, cost, retailPrice, orderStatuspart.updated
F&I Contract/dealers/{dealerId}/fnidealNumber, financeType, lender, products, contractStatus—
Employee/dealers/{dealerId}/employeesemployeeId, name, role, department—
Integration status

Real-Time Visibility Into Every Connection

Developers get a live status view of the API, webhook delivery, and each DMS connector — alongside logs and error details in the Integration Console.

All core systems operationallast 60 days
Unified API
Operational
Webhook delivery
Operational
Scheduled data feeds
Operational
CDK connector
Operational
Reynolds & Reynolds connector
Operational
Dealertrack connector
Operational
Tekion connector
Operational
PBS connector
Degraded

Illustrative status view with sample data

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.