Skip to main content

TVM Source (Team Velocity)

Team Velocity builds dealer websites for several OEMs' franchise networks, and the inventory API behind those sites is public. One raw asset per market reads it:

assetrowsraw source
<oem>/<market>/raw/tvm_dealer_listingsone per VIN in a dealer's new-vehicle listingai_public_api.dealer_providers.tvm:inventory_from_website_platform

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

Dealers​

The dealers are the rows whose platform is team_velocity in the website_platform partition with the raw partition's key, 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_id and a campaign_id. The asset raises on a team_velocity row missing either id, and on an account_id listed under more than one dealer code. Each row has the OEM's own dealer code, so the raw rows join to the OEM's dealer table without a crosswalk.

Credentials​

None. No API key, no token, no session.

Dealer identifiers​

AccountId is what scopes a request to a dealer: two accounts return disjoint VIN sets, and an account returns its own vehicles regardless of the campaign paired with it.

Both ids are inlined in the page source of the dealer's own site, so a plain fetch of the homepage yields them:

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.mbofmodesto.com/ | grep -oiE '(accountid|campaignid)\D{0,8}[0-9]{3,7}' | sort -u

A dealer's homepage can answer 403 on one day and serve both ids on another. A 403 means retry, not that the ids live elsewhere.

Origin is not enforced​

The API returns identical results for a request whose Origin is:

  • the dealer's real domain
  • an OEM vanity domain
  • a different dealer's domain
  • a dealer of a different OEM
  • example.com
  • absent entirely

This was measured on both the VIN listing and the per-VIN detail endpoint, with the detail responses byte-identical.

domain is the domain column of the dealer's website_platform row with an https:// prefix. It therefore only populates the Origin and Referer headers, which the API ignores. It reaches no URL, query parameter, or auth path.

CampaignId must be present but its value is ignored​

Pairing an AccountId with another dealer's CampaignId returned that account's own vehicle list unchanged across all 20 mismatched pairs tested. Omitting the parameter is a different matter: three accounts whose correct pair returns 182, 582, and 561 vehicles each returned 1 vehicle with CampaignId absent. The component always sends it, so this is a constraint on hand-rolled probes rather than on the asset.

Volume​

Two phases: one listing call per dealer, then one detail call per VIN in the dealer's new-vehicle listing. Each detail call writes one raw row, so a VIN listed on two dealers' sites has two raw rows.

Transformed tier​

<oem>/<market>/transformed/tvm_inventory holds one row per VIN.

ai_public_api.dealer_providers.tvm.extract_inventory parses a detail response into a TVMVehicle. A response that is not a JSON object produces no row. The columns shared by every dealer-website source are described in Dealer-Website Inventory.

  • provider_site_id is the AccountId queried.
  • provider_dealer_id is the response's dealerID, the account of the rooftop holding the vehicle. A group site's VIN listing includes its sister stores' vehicles, so a VIN arrives once for each site that lists it. In one MBUSA partition, 1,990 rows held 1,479 VINs.
  • site_dealer_code is the dealer_code the raw request recorded.

The platform_params of the dealer's website_platform row holds its account id. A dealer's site and its rooftop have the same account id.