CDK Global API

Overview

CDK Global is the largest dealer management system vendor in North America, used by roughly half of all franchised auto dealerships in the United States. Its platform covers inventory management, deal processing, finance and insurance, repair orders, CRM, and accounting. Because of that market concentration, CDK is a required integration target for nearly every automotive retail technology product: inventory aggregators, AI pricing engines, service drive tools, F&I compliance platforms, and CRM systems all encounter CDK at a significant share of their target dealer customers.

The CDK 3rd-Party Access (3PA) program gates every API connection. Enrollment requires a formal application and a partner review by CDK, after which the dealer pays a monthly per-connection fee on top of the third-party product's own pricing. This fee structure puts the cost decision on the dealer rather than the developer, which means that even after a team completes the partner enrollment, each dealer integration requires a separate commercial conversation about the connection fee. The automotive tech community and regulators have examined CDK's integration access model on antitrust grounds: the 3PA program's per-connection fee structure and approval requirements have been subjects of regulatory scrutiny and industry complaints, though the access model itself has not changed as a result. For a team building on CDK data, this is a structural market condition rather than a temporary developer experience gap.

In June 2024, a cyberattack shut down CDK's systems across approximately 15,000 dealerships for roughly two weeks, forcing dealers to revert to manual processes for sales and service. The incident is operationally relevant for automotive tech teams because it accelerated demand for integration paths that do not depend solely on CDK's infrastructure, and because CDK added elevated security review requirements to the 3PA program following the breach. Integuru generates a production-ready HTTP API for CDK Global using direct HTTP requests against the same endpoints the CDK web application uses internally. Inventory records, deal data, service orders, customer CRM, and F&I workflows are all reachable without a 3PA agreement, and the Production plan includes 24/7 on-call maintenance to handle authentication and endpoint changes before they affect your production calls.

---

Why Teams Need This Integration

CDK's market position makes it unavoidable for automotive retail tech, and the 3PA fee structure makes it expensive to access through official channels before a product has revenue.

Inventory aggregators and pricing engines. AI vehicle pricing tools, inventory listing syndication platforms, and retail price optimization products need a live, queryable vehicle roster. list_vehicles and get_vehicle_detail return the inventory layer with VIN, pricing, trim, mileage, and days on lot. A pricing engine that cannot pull real-time CDK inventory without a per-dealer 3PA fee is commercially limited before it ships its first customer, because that fee becomes a sales objection on every dealer conversation.

AI service advisors and service drive automation. Service lane AI tools that predict maintenance needs, generate recommended service items, or auto-generate repair order documentation depend on list_service_orders and get_service_order_detail to read the current repair order state. create_service_order gives these tools write access to open new repair orders without a service advisor manually entering the data. Every CDK-based dealership that adopts a service AI tool faces the 3PA barrier before the tool can read or write a single repair order.

F&I compliance and product penetration tools. Finance and insurance technology platforms that track product penetration rates, generate compliance reports, or recommend F&I menus need get_fi_menu and submit_fi_contract to read deal-level F&I data and push back signed contracts. The compliance stakes in F&I are high enough that teams building in this space cannot afford brittle integrations, yet the 3PA program gives them no faster official path.

CRM sync and customer engagement platforms. Automotive CRM platforms that centralize customer communication across sales and service need list_customers, get_customer_detail, and create_customer to maintain a live roster tied to CDK's deal and service history. CRM tools that rely on nightly CSV exports from CDK go stale between runs; programmatic access through Integuru gives them a query-on-demand path instead.

---

DMS Workflows This Integration Covers

The fourteen planned actions cover the full CDK operational loop across inventory, deals, service, CRM, and F&I:

• Inventory management: list_vehicles and get_vehicle_detail surface the live inventory with VIN, pricing, options, and reconditioning status. update_vehicle_status gives downstream tools write access to update pricing and availability without a human touching the CDK interface.
• Deal management: list_deals and get_deal_detail return active and closed deal records with customer, vehicle, financing terms, and F&I product data. create_deal opens new deal records for sales tools and desking applications.
• Service orders: list_service_orders and get_service_order_detail cover the repair order layer with labor operations, parts, and technician assignments. create_service_order gives external service tools write access to the CDK service drive.
• CRM and customer data: list_customers, get_customer_detail, and create_customer support CRM sync, lead intake, and customer engagement tools that need a live, writable customer roster.
• F&I processing: get_fi_menu retrieves available F&I products and pricing for a deal. submit_fi_contract pushes signed contracts back against the deal record for compliance and contracting automation tools.

---

Adjacent Integrations

Integuru does not currently have live automotive-specific integrations. The reverse-engineering approach Integuru uses has been proven across equally complex enterprise platforms in adjacent verticals. The Modmed integration covers 21 live actions across a cloud EHR platform with comparable authentication complexity, multi-session management, and data sensitivity requirements. The NextGen integration delivers 10 live actions for a healthcare platform serving multi-location practices, the same multi-account pattern that applies to dealer groups running CDK across multiple rooftops. The eClinicalWorks integration handles a large enterprise platform with strict session management, demonstrating the same reliability model that CDK's authenticated web application requires.

For service department workforce operations that run alongside CDK, the Workeasy integration provides live access to shift scheduling and workforce data. The HomeBase integration covers employee management and timesheets for service drive staffing workflows.