Skip to main content

DealerOn Source

DealerOn builds dealer websites for several OEMs' franchise networks. A DealerOn search page holds no vehicles of its own: the browser requests them from a JSON endpoint, and that endpoint is public. Two raw assets per market read it: one resolves each dealer's search page, the other pages that dealer's vehicle endpoint.

assetrowsraw source
<oem>/<market>/raw/dealer_on_search_pagesone per search page readai_public_api.dealer_providers.dealer_on:SEARCH_PAGES
<oem>/<market>/raw/dealer_on_dealer_listingsone per page of 96 vehiclesai_public_api.dealer_providers.dealer_on:INVENTORY

The search-pages asset reads the market's dealers/website_platform, described in Dealer website platform classification, and holds the dlron-srp-model JSON of each search page it reads, with the page's path as _request_url. The listings asset reads the search-pages asset for the DealerId, PageId and stocked count in those rows, and its rows' _request_params hold the dealer_code and page_id paged.

Which search pages​

A dealer is read from its all-vehicles page, /searchall.aspx, whose model must state PageVehicleType NewAndUsed. The raw listings therefore hold new and used vehicles.

A dealer's new-vehicle page can leave out new vehicles. Its BaseFilter, the page's stored filter, can exclude models, body types or stock numbers besides used vehicles. At MBUSA dealer 62148, BaseFilter type = 'n' and (stocknum notlike '%l') leaves out the new vehicles whose stock numbers end in L, which the dealer's comments describe as courtesy vehicles.

When the all-vehicles page has no dlron-srp-model, or states another PageVehicleType, the dealer is read from its new-vehicle page, /searchnew.aspx, and its used-vehicle page, /searchused.aspx, which must state New and Used. Each page that does not resolve is recorded as a failed request, and the dealer's other page still yields its row.

Every dealer's all-vehicles page is requested under one worker pool, then the new- and used-vehicle pages of the dealers that need them under a second.

Dealers​

The dealers are the website_platform rows of the same partition whose platform is dealeron, except the rows of dealers whose websites redirected to another dealer's site, as described in Dealer website platform classification. Each such row's platform_params holds a dealer_id. The search-pages asset raises on a dealeron row without one, and on a dealer_id listed under two dealer codes. The search-pages asset requests each row's domain. No dealer file is checked in.

Credentials​

None. No API key, no token, no session. A plain User-Agent is served. DealerOn does not fingerprint the TLS handshake, which is what Dealer Inspire and Dealer eProcess use to refuse a request whose headers look like a browser's.

Dealer identifiers​

Two identifiers address the endpoint: a DealerId and a PageId. DealerId identifies the dealer's DealerOn account; PageId belongs to an individual search page.

Both are in the search page itself, in a dlron-srp-model script element carrying the page's JSON model:

curl -s --http2 -L --compressed -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" https://www.gunncdjr.com/searchnew.aspx \
| grep -o "<script id='dlron-srp-model'.*</script>" | head -c 400

The model also carries SearchResultsListModel.ResultsCount, the dealer's stocked count.

DealerId is the value website_platform records as platform_params.dealer_id, as a string. When a search page reports a different DealerId, the search-pages asset records the dealer as a failed request with reason dealer_id_mismatch.

A homepage can load files from more than one DealerOn account: a group site loads its group's shared logo and background from the account that hosts them. The classifier therefore takes the most frequent /static/dealer-N/ account on the homepage.

Search page redirects​

On many dealer sites /searchnew.aspx answers 301 with a per-dealer URL rather than serving the page itself. The 301 body is zero-length, so a client that does not follow redirects sees no dlron-srp-model.

The target's URL does not say which inventory it searches. On crenwelgemotors.net, /searchnew.aspx redirects to /car-dealership-kerrville-TX.html, which reads like a homepage and is a new-vehicle SRP. The model's PageVehicleType holds the inventory type:

  • New on /searchnew.aspx and its redirect targets
  • Used on /searchused.aspx
  • NewAndUsed on /searchall.aspx

Recognizing a DealerOn site​

Every DealerOn response carries x-dealeron and x-dealeron-surrogate-keys headers, alongside server: nginx and x-powered-by: ASP.NET. The headers are present on error responses too — an unknown path answers 404 and still carries them. The body of a served page repeats dlron and dealeron dozens of times.

A domain that is not on DealerOn carries none of these. Across six Stellantis dealers on other platforms, /searchnew.aspx answered 403 from the site's CDN — Cloudflare (cf-mitigated: challenge) for the Dealer Inspire dealers, Akamai for the TVM ones. That 403 is path-independent: the root and a nonsense path answer it too, so it reflects a bot challenge ahead of routing rather than a missing /searchnew.aspx.

PageId is not validated against DealerId​

PageId names a stored search configuration — chiefly the vehicle-condition filter. The endpoint does not check that it belongs to the DealerId beside it in the path. DealerId and domain decide whose inventory answers; PageId decides which slice of it. Measured against DealerId=24210 on gunncdjr.com:

PageIdsourceHTTPTotalCountconditions on page 1
2314960that dealer's /searchnew.aspx200236New 96/96
2314961one above it200236New 96/96, a different 96-VIN subset
2314991that dealer's /searchall.aspx200893Used 70, New 26
2314992that dealer's /searchused.aspx200657Used 96/96
2512013another dealer's /searchnew.aspx200236byte-identical to 2314960
2512045another dealer's /searchused.aspx200657Used 96/96
0, 1, 999999999invented404—HTML error page

A PageId that exists nowhere answers 404. Any other PageId answers 200 with well-formed JSON, the right dealer's vehicles, a TotalCount matching its own slice, and the same card schema — including the used-vehicle slice, under a new-vehicle PageId's place in the path. Nothing in the response distinguishes it from the intended one.

The endpoint​

GET /api/vhcliaa/vehicle-pages/cosmos/srp/vehicles/{DealerId}/{PageId}?pt={page}&pn={size}

pt is the 1-indexed page number and pn the page size. Every response repeats the dealer's full result count at Paging.PaginationDataModel.TotalCount, which sizes the remaining pages.

Vehicles are in DisplayCards, one entry per card. A card is either an ad slot (IsAdCard) or a VehicleCard.

Page size​

pn accepts 12, 24, 48 and 96. The endpoint serves any other value as 12, and reports PageSize: 12 in the response. It returns no error, so a mistyped pn costs eight times the requests and nothing raises. 96 is the largest accepted size.

Empty results​

A search page with no vehicles responds with a zero-length body rather than JSON holding an empty array. A page requested past the end of a result set responds the same way. Neither body carries a TotalCount, so neither can size a result set on its own.

Volume​

Reading a dealer out takes one search-page request, or three when it has no all-vehicles page, plus one endpoint call per 96 vehicles.

Vehicle fields​

A card carries the whole vehicle, so there is no per-VIN detail fetch. Beyond VIN, year, make, model, trim, stock number, MSRP, mileage and both colors, the fields worth naming:

  • StellantisCode — the OEM's own configuration code, present on roughly 94% of cards. It is absent on most in-transit vehicles.
  • VehicleModelCode — the model code, present on every card, including the cards that carry no StellantisCode.
  • VehicleTaggingInventoryDate — the date the vehicle entered inventory.
  • VehicleInStock, VehicleInTransit, VehicleInProduction — disjoint status flags, restated as text in VehicleStatusModel.StatusText.
  • VehiclePriceLibrary — a base64 string holding the price breakdown: MSRP, internet price, selling price and the itemized incentives.
  • ChromeStyleId — the Chrome Data style, for joining to a catalog.

Transformed tier​

<oem>/<market>/transformed/dealer_on_inventory holds one row per VIN. ai_public_api.dealer_providers.dealer_on.extract_inventory parses each vehicle card whose VehicleCondition is New into a DealerOnVehicle, and skips ad cards and used vehicles. ccode holds StellantisCode, and price holds the Selling Price from VehiclePriceLibrary. The columns shared by every dealer-website source are described in Dealer-Website Inventory.

  • provider_site_id is the card's DealerId, the site queried.
  • provider_dealer_id is DealerLocatedAtId, the rooftop holding the vehicle. A group site lists its sister stores' vehicles under its own DealerId. In one partition, 3,515 of the 11,164 vehicle cards were held by a sister store.
  • site_dealer_code is the dealer_code the raw request recorded.
  • in_stock is VehicleInStock and in_transit is VehicleInTransit. A card sets at most one of VehicleInStock, VehicleInTransit and VehicleInProduction, so a vehicle in production has in_stock and in_transit both false. Only in_stock marks a vehicle on the lot.

A dealer's site and its rooftop have the same DealerId.

The rendered page is a poorer source​

The search page also carries an ItemList in ld+json, and each vehicle detail page carries a Vehicle. Both hold fewer fields than the endpoint:

  • The ItemList has VIN, name and image only, at 12 entries per page with no page-size control.
  • The Vehicle adds a price and an equipment description, and has no stock number, colors, model code or dates.

Reading one dealer's 238 vehicles through those two took 21 requests. The endpoint returns the same 238 vehicles, with more fields on each, in 3.