DealerSocket
DealerSocket is an automotive dealership CRM and Dealer Management System (DMS) software platform for franchise and independent auto dealers, covering customer relationship management, inventory management, websites, digital marketing, and desking/deals. DealerSocket is a Solera company (acquired 2021; part of Solera's Vehicle Solutions line of business). DealerSocket exposes a set of inbound and outbound integration APIs - lead forwarding, deal push to the DMS, customer updates, activity and CTI/call logging - but access is not self-serve. It is delivered through DealerSocket's Certified Partners program (launched 2013, 500-plus integration points) and is application-, contract-, and certification-gated. There is no public developer portal, no published authentication reference, and no public endpoint or base-URL documentation; the logical APIs below are modeled from DealerSocket's public integrations page rather than a self-serve API reference.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles DealerSocket the way a machine reads it — 5 machine-readable artifacts across 4 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — DealerSocket scores 10.5/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile DealerSocket
Each block below is one kind of artifact we hold for DealerSocket. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 4
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
DealerSocket CRM & Leads API
Lead and CRM integration surface. Includes the outbound Lead Forwarding Service (forwards incoming and processed dealership lead data to a third-party vendor as XML or email), i...
DealerSocket Customers API
Inbound customer integration surface. The Customer Update integration modifies customer records in DealerSocket CRM (with insert of not-yet-found customers noted as forthcoming ...
DealerSocket Deals & Desking API
Outbound deal integration surface. Deal Push Basic performs a one-way push of basic deal data (customer, co-buyer, salesperson, and vehicle of interest) to the DMS, and Deal Pus...
DealerSocket CTI & Activity Logging API
Inbound call-tracking and activity-logging surface. CTI Direct Post logs inbound and outbound call information for activity tracking, Call Vendor Direct Post Work Note Update ap...
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for DealerSocket — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Access & Security 1
Authentication, authorization, and security posture
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/dealersocket · machine-readable index on apis.io