Skip to main content

Dealer.com Source

Dealer.com builds dealer websites for several OEMs' franchise networks. Each site serves its vehicles from a JSON endpoint on the dealer's own host. Two raw assets per market read it:

assetrowsraw source
<oem>/<market>/raw/dealer_com_search_pagesone per dealerai_public_api.dealer_providers.dealer_com:search_pages
<oem>/<market>/raw/dealer_com_dealer_listingsone per endpoint responseai_public_api.dealer_providers.dealer_com:inventory

The search-pages asset reads the market's dealers/website_platform, described in Dealer website platform classification. The listings asset reads the search-pages asset.

Dealers​

The dealers are the website_platform rows of the same partition whose platform is dealer_com, 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 an account. The search-pages asset raises on a dealer_com row without one, and on an account listed under two dealer codes. That account is the site's siteId. The search-pages asset requests each row's domain. No dealer file is checked in.

Credentials​

Dealer.com asks for none. Every request goes through AkamaiSession, which impersonates a browser's TLS handshake with curl_cffi. The search-page request sends Referer: https://www.google.com/.

The Zyte fallback in Pacing uses the DEALER_WEBSITE Zyte key described under Credentials in the website platform doc.

Each asset's params set the key's prefix (zyte_key_prefix: DEALER_WEBSITE) and the oem tag of each Zyte request. The market tag is the market that PublicApiRawComponent infers from the defs path.

The search page​

/new-inventory/index.htm is a site's new-vehicle search page. A script on the page holds the request state that the page's JavaScript sends to the endpoint:

DDC.WS.state['ws-inv-data']['inventory-data-bus2'] = {"moreRequestData": {...}, "WIS": {...}, "requestData": {...}, "prefs": {...}, ...};

A raw row holds that object's moreRequestData, requestData and prefs, the window id (inventory-data-bus2), and WIS.pageInfo. The rest of WIS holds the page's first vehicles, its incentives and its facets, about 430 KB. The endpoint returns all of them again.

A site can give its new-vehicle page its own pageAlias, such as SITEBUILDER_NEW_INVENTORY_1. Whatever the pageAlias, the page's prefs restrict the listing to new vehicles.

A service and parts site has no new-vehicle inventory, and its navigation links to no inventory page. The asset requests /new-inventory/index.htm on every Dealer.com site; on such a site, Dealer.com answers with its no-results listing. For dealer 25154 (www.indymb.com, Silver Star Service & Body Shop), the request redirects to /all-inventory/no-results.htm?category=AUTO. That page holds no ws-inv-data script, and its pageAlias starts with INVENTORY_LISTING_NO_RESULTS_; here it is INVENTORY_LISTING_NO_RESULTS_AUTO. The search-pages asset writes no row for such a site, so the listings asset does not request its pages. The site is recorded as a successful fetch attempt with the reason no_inventory_listing.

The page also depends on where the request comes from. From Dagster+ in AWS, dealer 25154's /new-inventory/index.htm does not redirect. It is a listing page with the pageAlias INVENTORY_LISTING_DEFAULT_AUTO_NEW and no ws-inv-data script. Most sites with inventory use the same pageAlias, so the page alone does not show that the site lists no vehicles. The excluded_dealer_codes param of the search-pages raw source names such dealers, and the asset does not request their sites. For Mercedes, the dealer_com_excluded_dealer_codes template variable sets it to ["25154"].

Any other dealer whose page yields no state is recorded as a failed fetch attempt with one of these reasons:

reasonmeaning
unreachableno 2xx response
no_inventory_stateno ws-inv-data script on the page, which classify does not identify as another platform's
platform_mismatchno ws-inv-data script, and website_platform's classify identifies the page as another platform's
malformed_stateafter the retries in Pacing, the script still does not parse or still lacks one of the keys above
site_id_mismatchmoreRequestData.siteId is not the account from website_platform

The fetch_attempts check counts every reason except platform_mismatch as a terminal failure. A platform_mismatch dealer's site has switched from Dealer.com to another platform since website_platform last read its homepage, so the asset has nothing to read there.

The endpoint​

POST https://<domain>/api/widget/ws-inv-data/getInventory
{
"siteId": "davidtaylorchryslerdodgejeepramcllc",
"pageAlias": "INVENTORY_LISTING_DEFAULT_AUTO_NEW",
"windowId": "inventory-data-bus2",
"widgetName": "ws-inv-data",
"includePricing": true,
"preferences": {"listing.config.id": "auto-new", "...": "...", "pageSize": "48"},
"inventoryParameters": {"accountId": ["davidtaylorchryslerdodgejeepramcllc"], "start": ["0"]}
}
  • preferences replaces the page's display preferences as a whole. Its listing.config.id holds the new-vehicle filter, and its value differs between dealers (auto-new, auto-new,auto-custom, auto-jeep-gc-lowhi,auto-lhm-shared-new). A preferences that holds only pageSize lists used vehicles too, so a request repeats every key of the page's prefs. inventoryParameters.type does not filter.
  • pageSize has a ceiling of 48: 100 and 250 both return 48.
  • start is the 0-indexed offset of the first vehicle.
  • Every response reports the result count at pageInfo.totalCount, which gives the number of pages to request.
  • pricing is present only with includePricing: true.
  • accountId restricts the listing to one rooftop; see Group sites.
  • The display preferences do not remove fields from the response. A page of 48 vehicles is 670–930 KB, and images are about half of those bytes.

The GET /apis/widget/INVENTORY_LISTING_DEFAULT_AUTO_NEW:inventory-data-bus1/getInventory path that the page still names returns Legacy inventory endpoints are deprecated and no longer return data.

Group sites​

A group's sites can list every rooftop's vehicles. The Mayfield, Benton and Murray David Taylor sites (60801, 27160, 60580) each list the same 139 vehicles, each vehicle under the accountId of the rooftop that holds it. With accountId set to the site's own siteId, a site lists only its own rooftop's vehicles, so a group's vehicles are read once, from each rooftop's own site.

A rooftop with no website_platform row is therefore not read. Larry H. Miller CDJR 104th (26880) has no website in the dealer locator, and its vehicles appear only on Larry H. Miller Colorado Jeep's site (60656).

Rooftops and dealer codes​

accounts.<accountId>.dealerCodes lists the rooftop's codes at other systems. The Stellantis dealer code is the entry whose codeType is cllc on a Chrysler, Dodge, Jeep or Ram account (…cllc), and ar on an Alfa Romeo account (…fcaar).

Spotlighted vehicles​

A page can repeat a few spotlighted vehicles in addition to its 48, so a site's pages can hold more vehicles than totalCount. The number of unique VINs across a site's pages equals totalCount.

Pacing​

One Throttle spaces requests 0.15 s apart across a pool of 32 workers, because dealer domains share Dealer.com's edge servers.

The session makes a search-page request up to 10 times (SEARCH_PAGE_ATTEMPTS), and a listings request up to 6 times (REFUSAL_ATTEMPTS, the limit website_platform also uses). It retries the request on:

  • a 403 response, with no wait;
  • a 429 response to a search-page request, with no wait;
  • a 429 response to a listings request, or a 5xx response, after waits of 5, 10 and 20 s, then 30 s before each later attempt;
  • one of these curl errors, after the same waits:
    • 28 (OPERATION_TIMEDOUT), a timeout;
    • 18 (PARTIAL_FILE), a response body shorter than its Content-Length;
    • 56 (RECV_ERROR), a connection that fails while receiving data;
    • 35 (SSL_CONNECT_ERROR), a failed TLS handshake;
  • a search page whose ws-inv-data script does not parse or lacks one of the keys in The search page, after the same waits.

Each retry opens a new session with an impersonation profile that the request has not used yet. The profiles come from website_platform's IMPERSONATION_PROFILES. Each wait pauses the whole pool.

Akamai answers about 44% of search-page requests with a 429 (Server: AkamaiGHost, body Too many requests), whatever the request rate. The 429s do not cluster in time, do not repeat on the same dealer and do not depend on the impersonation profile. A wait therefore does not make the next attempt more likely to succeed, so the session retries a search-page 429 at once. The attempt limit sets the share of dealers that every attempt refuses: about 0.44^10, or 0.03%.

Zyte sends its requests from other IP addresses. When a request's last AkamaiSession attempt receives a 403 or a 429, the search-pages asset and the listings asset request the page again through Zyte. These statuses are ZYTE_FALLBACK_STATUSES, which website_platform also sends to Zyte.

  • A 2xx search page from Zyte replaces the failed one.
  • When the failed listings page is the site's first page, the asset requests every page of the site through Zyte, because the site's page count comes from the first page.

Zyte retries gives the number of Zyte attempts and the waits between them. A search page from Zyte whose ws-inv-data script does not parse or lacks one of the keys in The search page is retried after the same waits as a 5xx from Zyte. When the page is still malformed after the last Zyte attempt, the site's fetch attempt is recorded with the reason malformed_state.

The search-pages asset then requests each page whose reason is still unreachable or malformed_state again in a deferred sweep. The deferred sweep starts DEFERRED_SWEEP_DELAY_SECONDS (ai_http.deferred) after the direct and Zyte requests finish. It requests each page directly, on new sessions, with the same attempt limit. A page's result in the deferred sweep replaces its earlier result.

The search-pages asset logs each retry with its cause, such as http_429 or malformed_state. The message for a 429 or 5xx response includes the values of the response's Retry-After and Server headers. The message for a 403 response includes the value of its Server header. When it finishes, it logs the number of retries for each cause.

The search-pages asset also logs the status of each site whose search page Zyte did not return.

A malformed_state message names the request-state key that is missing, null or of the wrong type, such as WIS is null. The message also gives the page's length in characters and the request state's top-level keys.

The listings asset gives its Throttle a RequestMeter. When the asset finishes its AkamaiSession requests, it logs the meter's summary:

  • the number of requests;
  • the largest number of requests sent in one second;
  • for each wait, its length and the number of requests sent in the 1, 30, 60, 120 and 300 s before it. The summary calls the waits penalties.

The summary includes the wait before a retry of any cause. A retry after a 403 has no wait, so the summary does not include it.

Akamai​

Each site is served through Akamai, which refuses a client whose TLS handshake does not match a browser's. A request sent with httpx receives a 403 response with Server: AkamaiGHost, with or without a browser User-Agent. AkamaiSession sends its requests with curl_cffi, which impersonates Chrome.

Vehicle fields​

  • modelCode and optionCodes: the Stellantis sales codes, such as WLTH74.
  • trackingAttributes: packageCode, cCode, colors, engine, transmission and drive line.
  • pricing.dprice: MSRP, dealer discount, fees, incentives and the final price. The final price is the entry with isFinalPrice: true, which is not always the last entry.
  • inventoryDate: a date in MM/DD/YYYY format when the request repeats the page's prefs.
  • chromeId, stockNumber, status, type, link, uuid and accountId.

Transformed tier​

<oem>/<market>/transformed/dealer_com_inventory holds one row per VIN. ai_public_api.dealer_providers.dealer_com.extract_inventory parses each vehicle of a listings page into a DealerComVehicle. It drops each vehicle whose type is not new, because a site's new-vehicle listing can include used vehicles. The columns shared by every dealer-website source are described in Dealer-Website Inventory.

  • provider_site_id is the site_id the raw request recorded, the site queried.
  • provider_dealer_id is the vehicle's accountId, the rooftop holding it. A request that restricts accountId to the site's own can still return vehicles held under another account.
  • site_dealer_code is the dealer_code the raw request recorded.
  • dealer_code is the holding rooftop's Stellantis dealer code: the cllc entry, or else the ar entry, of accounts.<accountId>.dealerCodes on the same page, with surrounding spaces removed. It is null where the account has neither.
  • in_stock is true where status is live or on_deposit. in_transit is true where status is in_transit. A vehicle whose status is in_transit_at_factory is in production, so both are false. Both are null for any other status.
  • price is trackingPricing.internetPrice, null where it is 0.
  • msrp is trackingPricing.msrp.
  • exterior_color, interior_color, drivetrain (driveLine), engine, transmission, mileage (odometer) and ccode (cCode) come from trackingAttributes. The colors are the site's own text, and the listings give no color codes.
  • factory_codes is optionCodes.
  • date_in_stock is inventoryDate, written MM/DD/YYYY or as Fri Aug 08, 2025.
  • vdp_url is link, a path on the site's host.