The Keyloop API: what it offers and what an AI agent needs from it.

What is Keyloop

Keyloop is a dealer software company with roots in Kerridge, founded in Hungerford in the UK more than four decades ago. It later traded as ADP Dealer Services and CDK Global across the UK, Europe, the Middle East, Africa and Asia, and was renamed Keyloop after Francisco Partners acquired it in 2021.

Its dealer management systems include Keyloop Autoline (formerly Kerridge Autoline) and Keyloop Drive (formerly Autoline Drive). On top sits Fusion, Keyloop's automotive retail platform, with Sales Hub, Acquisition Hub, Vehicle Hub and Service Hub. By Keyloop's own count, Fusion serves more than 20,000 retailers and more than 80 OEMs. In 2026 Keyloop bought Motortech.ai, maker of the AIME sales agent.

Which Keyloop APIs exist

Keyloop's developer portal describes an open platform with one interface to its DMSs across Europe, the Middle East, Africa and Asia. Availability differs per DMS, and not every endpoint or field exists on every system; each product page lists the systems it covers. The products a customer-facing agent touches most:

How access works

• 01Join Keyloop's Partner Programme. Keyloop assigns a partner programme manager who takes the integrator through Keyloop's security review.
• 02Build against the API layer; Keyloop helps test data integrity between the two systems.
• 03Pilot at a live dealer. Sign-off needs the partner, the dealer and Keyloop.
• 04Access is then granted per contract and per dealer code. Which brands and branches a partner may read is decided by the dealer and Keyloop, so adding a rooftop is an entitlement request to Keyloop, not a new project.
• 05Nothing is installed on the dealer's servers and no database is opened; the integrator connects to Keyloop's gateway from its own infrastructure.

What an AI service agent needs from the Keyloop API

Pitfalls we see in production

• 01Service products with zero allowed time. They cannot anchor a booking on their own; ride them along as additional services and flag them to the dealer.
• 02Advisor records per brand. A multi-brand site can hold one advisor under several brand codes, and an advisor who has left can still own a diary. Offering the wrong one books a slot nobody works.
• 03Empty availability means two different things. A dead capacity feed and a genuinely full window both return an empty list; the first should not stop bookings across a network, the second must. Probe further ahead before deciding which.
• 04Creating an appointment is not idempotent. A retry after a timeout can book the same customer twice, so never retry the create blindly; check first.
• 05The appointment record is thin. It does not carry the jobs, labour lines and workshop planning; read the repair order for status and planning.
• 06Labour codes and job lines are not written by the booking API. The customer's symptom goes into the appointment notes; the advisor adds job lines in the DMS.
• 07Configuration drifts. A product missing at one branch, opening hours that do not match the diary, a renamed branch. Audit every branch before go-live with real test bookings, and keep the checks running afterwards.

What Salesteq runs on the Keyloop API today

BMW, Ford and Hyundai service in Saudi Arabia book through Salesteq into Keyloop Autoline across 29 service centres, in Arabic and English, from WhatsApp, the brand website and the phone menu. The agent finds the customer and car, picks the service products, reads live capacity, writes the appointment with branch, advisor and workshop time, confirms it by SMS or WhatsApp, and moves, cancels or checks it on request. At BMW about 8 in 10 service bookings now come in online.

Bookings are audited against the repair orders branch by branch, so a wrong branch, a missing advisor or a placeholder workshop time is caught by us, not by the customer on the day. On the sales side, test drives and enquiries go into the Keyloop CRM with the conversation.

Questions about the Keyloop API