DOCUMENTATION

Build your first integration.

Authenticate, call the APIs, choose formats, and handle production responses.

Your first API request

Create an account, copy the credential shown once, and place it in a server-side environment variable or secrets manager.

Keep registered credentials private

Never embed a registered customer API key in browser JavaScript, a public mobile bundle, or source control. The documented ad_live_demo.keysecret credential is the public, rate-limited exception.

Decode a vehicle

Send a valid 17-character VIN and your bearer credential. VINs are normalized to uppercase and cannot contain I, O, or Q.

                
curl --request GET "https://autodealer.dev/api/service/vin/1HGCM82633A004352/json"
    --header "Authorization: Bearer $AUTODEALER_API_KEY" 
    --header "Accept: application/json"
                
            

Render the HTML vehicle report

Add one div with the VIN and your secure server-proxy URL. The widget requests the self-styled HTML fragment and renders the complete vehicle report inside that div.

                
<div id="vehicle-report"
    data-autodealer-vin-report
    data-api-key="ad_live_demo.keysecret"
    data-vin="1HGCM82633A004352"
    data-loading-text="Loading vehicle details...">
</div>

<script src="https://autodealer.dev/Scripts/autodealer-vin-report.js"></script>

VIN Decode endpoints

GET /api/service/vin/{vin}/json Complete JSON record
GET /api/service/vin/{vin}/xml Complete XML record
GET /api/service/vin/{vin}/html Embeddable HTML fragment

Response formats

VIN routes use explicit JSON, XML, and HTML format suffixes so clients always receive a predictable media type.