Kimoby API
Kimoby publishes a real REST reference with Basic auth, JSON Schemas and signed webhooks. Credential issuance is undocumented, the newer API version is handed out via dev-support email, and third parties need an accepted partner account.
Frequently asked questions
Kimoby scores C on Supergood's API Report Card. Kimoby publishes a real REST reference with Basic auth, JSON Schemas and signed webhooks. Credential issuance is undocumented, the newer API version is handed out via dev-support email, and third parties need an accepted partner account.
Kimoby has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Kimoby is a Quebec City company whose Dealership Engagement System (DES) and Service Lane OS run the customer-facing side of a dealership service department: two-way SMS, MMS and RCS texting tied to the repair order, video-to-customer, digital inspections and OP-code estimates with line-by-line approval, Kimoby Pay mobile and in-person payments with Affirm financing, Kimoby Go loaner and fleet management, Kimoby Grow recall and retention campaigns, Kimoby Voice AI missed-call handling and CSI surveys.
Automotive; franchised dealership service departments and dealer groups in Canada and the United States, with messaging limited to Canada, the US and Puerto Rico. Advisors work from a unified inbox where every text thread is tied to an open RO; they send inspection videos and estimates, collect approvals and payment links, and the results write back to the DMS.
More than 1,000 dealerships have run on Kimoby, with 747 in the current dataset (672 in Canada and 75 in the US), which makes it the leading Canadian service-lane vendor but a small US player against myKaarma, Xtime and TEXT2DRIVE (https://www.kimoby.com/kimoby-by-numbers, https://linkedin.com/company/kimoby).
Customer PII (name, E.164 cell numbers, email, address), full SMS and MMS conversation history, repair order and appointment data synced from the DMS, digital estimates and approvals, invoices and payment transactions (card data handled by Kimoby Pay, PCI scope), loaner vehicle telematics, and CSI survey responses.
Founded 2013; modern web and mobile apps with RCS support, AI video coaching in beta, OTA-connected loaners and AI voice. The public API is a v1 REST surface with JSON Schema definitions per resource; a newer version exists but is offered on demand only.
The current public docs describe v1 only; the vendor states additional capabilities exist in a newer version available on demand by emailing dev-support. Customers can easily opt out of messages, which one reviewer said rendered the system useless for internal reminders. Full sourced list under Sources below.
Common alternatives include myKaarma, Xtime, TEXT2DRIVE, Dealer-FX, UpdatePromise. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Not that we could find. There is no official Kimoby MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Kimoby doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.