Skip to main content
Premium Data Packages are optional, paid add-ons on top of any base plan. They unlock deeper, per-VIN data that we source from third-party providers at additional cost per request.
Disabled by default. Premium Data Packages are not included in any plan tier automatically. To enable a package on a dealership, contact your account manager or email support@autosnaplive.com.

​
How packages work

  • Per-dealership opt-in. Each dealership in your account can enable a package independently — you don’t have to turn them on account-wide.
  • Per-VIN billing. Packages meter on fetched VINs, not on API request count. See Usage & Billing.
  • Same auth, same gating. Premium Data Packages use the same API keys, same feature-gating, and same MCP tool surface as the rest of the platform. A package is just a feature flag on the dealership’s subscription.
  • Graceful denial. When a key or dealership isn’t entitled, requests return HTTP 403 with code: "FEATURE_NOT_AVAILABLE" — never silent or empty data. Your application can detect the gate and prompt for upgrade.

​
Available packages

Vehicle History & Records

Pre-owned vehicle history data — prior damage reports, title history, odometer records, service events, and a full verified history report PDF when available.Feature flag: history_report REST: GET /v2/vehicles/vin/{vin}/history-report MCP tool: get_vehicle_history_report

Dealer-Provided Documentation

Service records, window stickers, warranty paperwork, CPO inspection reports, brochures, and other dealer-attached documents for a specific VIN.Feature flag: documents REST: GET /v2/vehicles/vin/{vin}/documents MCP tool: get_vehicle_documents

Vehicle Marketing Context

Dealer-curated merchandising data per VIN — marketing-tag insights (low mileage, great price, rare color), local-market comparison summaries, and bundled CARFAX summary strings when present.Feature flag: marketing_context REST: GET /v2/vehicles/vin/{vin}/marketing-context

​
Vehicle History & Records

Returns available third-party history data for a used vehicle — the kind of record you’d normally expect to see referenced on a dealer’s Vehicle Detail Page. When a structured report is available for a VIN, the response includes:
  • A dedicated report URL (safe to surface to shoppers)
  • Structured report data: title history, odometer readings, damage/accident events, prior service activity, number of owners
  • A factory window-sticker-style summary when one is archived alongside the report
Not every VIN has a report available. Whether a report exists depends on both the dealer’s website provider (some platforms expose the signal, others do not) and whether the underlying report issuer has data for that specific VIN. When no report is found, the API returns has_report: false with data: null. Available for: select website providers — see Provider Coverage Map for the current list of supported platforms.

​
Dealer-Provided Documentation

Returns the set of documents a dealer has attached to a specific VIN — typically surfaced on their Vehicle Detail Page as downloadable links or embedded viewers. Common document types include:
  • Service history summaries
  • Factory window stickers and Monroney labels
  • Warranty documentation
  • CPO inspection checklists
  • Vehicle brochures
  • Market-value summaries
Document availability is per-dealership: only dealers on participating website platforms that publish document feeds will have documents returned. When the dealer does not participate, the API returns an empty document list. Available for: dealerships on participating website platforms. Contact your account manager to confirm coverage for a specific rooftop before enabling.

​
Vehicle Marketing Context

Returns the dealer’s own merchandising signals for a specific VIN — the kind of presentation context they’d surface on their own VDP. When available for a VIN, the response includes:
  • Marketing-tag insights — flags such as “low mileage for the model year,” “priced below the local average,” or “rare color combination,” each with the supporting comparison data (sample size, distribution percentiles, comparison radius)
  • Local-market comparison baggage — summary statistics for similar vehicles in the dealer’s local market (mileage and price distributions across the comparison cohort)
  • Vehicle and dealership context — basic vehicle specs and dealership branding the dealer publishes alongside the merchandising
  • CARFAX summary strings — passthrough of any CARFAX summary data the dealer’s merchandising stack has bundled with the VIN (single-owner flag, accident summary, report URL when available)
This data reflects how the dealer themselves describes the vehicle to shoppers — useful for assistants that want to mirror the dealer’s own positioning rather than offering an independent assessment. When the dealer does not subscribe to the underlying merchandising integration, or when the integration has no data for the VIN, the API returns has_data: false with data: null. Available for: dealerships subscribed to the underlying merchandising integration. Contact your account manager to confirm a specific rooftop is covered before enabling.

​
Enabling a package

Premium Data Packages are enabled at the dealership level. To turn one on for a specific dealership:
  1. Email support@autosnaplive.com with the dealership IDs and the package name(s) you want enabled
  2. Your account manager will confirm coverage, pricing, and billing terms for each dealership
  3. Once activated, the feature flag appears immediately — no redeploy required on your side
  4. Test with an as_test_... key first (test keys bypass all gating, so every package is callable regardless of entitlement)

Provider Coverage Map

Which website providers support which packages

Plans & Pricing

Base plan tiers (Essentials, Enhanced, Premium)

Test vs Live Keys

Test keys bypass all premium-package gating

Vehicle History Report endpoint

REST endpoint reference for Vehicle History & Records