Selly Automotive API
Selly Automotive is an AI-powered CRM and text-marketing platform built from the ground up for independent and Buy-Here-Pay-Here (BHPH) car dealers. This page is an independent design exercise that asks what a well-designed Selly Automotive API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed Selly Automotive API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing Selly Automotive product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
What is Selly Automotive?
Selly Automotive is an AI-powered CRM and text-marketing platform built from the ground up for independent and Buy-Here-Pay-Here (BHPH) car dealers. Dealers use Selly to capture every lead, centralize calls, texts, and emails in one inbox, automate follow-up sequences, run SMS text-blast campaigns, build branded payment proposals, and sync customer, sales, and inventory data with their DMS, all from web and mobile apps.
Core product areas include:
- CRM & Lead Management (unified lead capture across channels, smart call routing, pipeline organization)
- AI Lead Nurturing (automatic engagement, customizable follow-up sequences, intelligent agent alerts, appointment creation)
- Text & SMS Marketing (text-blast campaigns by vehicle interest, new-arrival and price-drop alerts, pre-built templates with tracking)
- Communication Platform (integrated calling, texting, and email plus a mobile app with driver's license and VIN scanning)
- Desking & Proposals (branded payment proposals, customizable down-payment defaults, payment-matrix and fee editor)
- Integrations (100+ integrations including inventory/XML ADF feeds and DMS sales-data sync with Frazer, Wayne Reaves, AutoManager, and more)
An API for a platform like this would naturally organize around its core data entities:
- Leads, Internet Lead Management (ILM) records, ADF/XML lead feeds
- Customers, Contacts, Communication History (calls, texts, emails)
- Deals, Payment Proposals, Down-Payment and Fee Configurations
- Appointments, Tasks, Follow-up Sequences
- Inventory and Vehicle records synced from the DMS, Text-Blast Campaigns
The Selly Automotive Integration Challenge
Independent dealers run daily sales operations on Selly, but turning its app- and integration-driven workflows into clean API-driven automation is non-trivial:
- No public developer API: Selly publishes no documented endpoints or developer portal, so programmatic access has to be, derived from the authenticated web and mobile apps
- Mobile-first data: Features like license and VIN scanning and on-the-go lead capture live in the native app, where data isn't exposed through any open web interface
- Partner-gated integrations: DMS, inventory, and lead-provider connections flow through Selly's 100+ partner network, each requiring a separate arrangement rather than a uniform API
- Mixed data formats: Inventory and lead data arrive as XML/ADF feeds while sales and CRM data live in the app, leaving no single normalized object model
- Session and authentication handling: Web and mobile sessions, login flows, and rate limits must be managed carefully for reliable headless automation
- Messaging compliance: Text-blast and automated SMS workflows carry opt-out and carrier-compliance requirements that any integration must respect
What a Selly Automotive API Could Look Like
If Selly Automotive exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like Selly Automotive: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/authenticateWould authenticate to a Selly Automotive dealership account using username/password, or MFA, and obtain a session token for downstream calls.
Leads
/leadsWould list leads and ILM records with filters for source, status, salesperson, and date range, including ADF/XML-sourced leads.
Leads
/create_leadWould create a new lead in Selly with contact details, vehicle interest, and source so it enters the follow-up pipeline.
Customers
/customersWould retrieve customer and contact records with their unified communication history across calls, texts, and emails.
Messaging
/send_textWould send an SMS or trigger a text-blast campaign to targeted customers, respecting opt-out and compliance rules.
Appointments
/appointmentsWould pull scheduled appointments and follow-up tasks generated by AI nurturing and manual workflows.
Use Cases
Sync leads and customers into your data warehouse
- Pull leads, ILM records, and ADF/XML feed entries from Selly into a single warehouse - Stream customer and communication history to downstream BI and reporting tools - Reconcile contacts across Selly and your DMS for a unified customer view
Automate lead capture and follow-up
- Push new web, marketplace, and walk-in leads into Selly's follow-up pipeline - Trigger AI nurturing sequences and create appointments without manual entry - Route high-value leads and agent alerts to the right salesperson automatically
Orchestrate text and SMS campaigns
- Launch targeted text-blast campaigns by vehicle interest or activity from external systems - Send new-arrival and price-drop alerts programmatically with template tracking - Capture replies and opt-outs back into customer records for compliant messaging
Keep deals and inventory in sync with the DMS
- Sync sales, deal, and payment-proposal data between Selly and your DMS in real time - Pull inventory and vehicle records to power lead matching and campaigns - Surface delinquent or stalled deals to retention and BHPH collection workflows
Technical Requirements
Authentication
Would require username/password and MFA with managed session handling across web and mobile surfaces
Connectivity
Would build on authenticated web and mobile app flows plus ADF/XML feed and DMS partner integrations where exposed
Response format
Normalized JSON across Leads, Customers, Deals, Appointments, and Messaging objects
Rate limits
Adaptive throttling tuned to your dealership account to avoid Selly-side limits
Session management
Would need automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for leads, customers, and messages with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for new leads, inbound messages, appointment changes, and deal updates
Latency
Design target: sub-second reads on cached entities; multi-second writes when posting messages and deal updates
Throughput
Design target: horizontally scaled workers sized to dealership lead and messaging volume
Reliability
Retry, backoff, and idempotency keys for lead creation, messaging, and deal writes
Versioning
Clear versioning and change management would matter as Selly Automotive evolves
Frequently asked questions
Yes. Data captured through the Selly mobile app, including license and VIN scanning, is surfaced through the same normalized API as the web app.
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual Selly Automotive product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.