Who the API is for
When it opens, partner access will be granted selectively — reviewed for security and compatibility before any credentials are issued.
Technology partners
DMS vendors, accounting platforms, and CRM providers that want to sync data with Dealer Suite 360 for a seamless dealer experience.
Enterprise dealers
Multi-location dealer groups that need to pull claims, inventory, and billing data into their own reporting and analytics tools.
Custom integrations
Dealerships and development teams building internal tools that need to read or write data to the Dealer Suite 360 platform.
What the partner API is designed to offer
The capabilities below describe the intended design of the partner API. They are on the roadmap — not live today.
RESTful API
Standard REST endpoints with JSON requests and responses, designed around bearer-token authentication with scoped keys per integration.
Webhook support
Event notifications for claim status changes, new units, and billing events are part of the design, with configurable retry logic for reliability.
Real-time data sync
Low-latency endpoints for claim status, inventory changes, and billing updates, with real-time streaming under consideration for live applications.
Developer documentation
An OpenAPI specification with endpoint documentation, code samples, and an isolated sandbox for testing is planned before any partner goes live.
How partner access will work
The intended path from first contact to a production integration. Details will be confirmed with partners as the program opens.
Register your interest
Tell us about your integration on the contact page. Our team reviews every request to confirm compatibility and security fit before the program opens to you.
Receive sandbox access
Approved partners receive sandbox credentials and access to the developer documentation, so you can build against sample data without touching any real dealer records.
Build in the sandbox
Develop and test your integration in an isolated sandbox with sample data. No live dealer data is accessible during development.
Production approval
Submit your integration for production review. Once approved, you receive production keys with agreed scopes and rate limits.
An illustrative request — not a live endpoint
The example below is illustrative only. It shows the shape a claims request might take once a partner API exists — it is not a live endpoint, and no endpoint like it is published today.
Request — a bearer-authenticated GET to a versioned claims endpoint (for example, GET /v1/claims on the API host), sent with an Authorization: Bearer <your_api_key> header and Content-Type: application/json, filtered by query parameters such as dealer_id, status, and claim_type.
Response — JSON containing a data array of claim records (each with fields like id, vin, and status) alongside pagination metadata (page, per_page, and a total count). Exact endpoints, fields, and authentication will be finalized with partners before any release.
Register your interest
There is no signup or credential issuance today — we are simply gathering interest from approved technology partners. Reach out through the contact page and tell us what you are building. Our team reviews every request and will follow up as the partner program takes shape.
To help us route your request, include:
- Your name and role
- Your company or organization
- What you are building and the integration use case
- Which data you would need to read or write, and how many dealers or units are in scope
No public Dealer Suite 360 API is live yet. If an integration is on your roadmap, register your interest on the contact page — we are gathering partners now and will reach out as the program opens.
API access questions
Is the API available today?
Not yet. There is no public Dealer Suite 360 API right now. We are gathering interest from approved technology partners and will open access as the partner program takes shape — register your interest on the contact page to be in the loop.
Who will be able to get access?
Approved technology partners, enterprise dealer groups, and vetted custom-integration teams. Every request is reviewed for security and compatibility before any credentials are issued.
What will it cost?
Pricing has not been set and we are not publishing figures before the program is live — no invented numbers. Commercial terms will be worked out with partners as the API opens.
How do I register my interest?
Use the contact page. Tell us who you are, what you are building, and which data you would need to read or write, and our team will follow up as the partner program opens.
