Docs / Data sources / NHTSA vPIC

NHTSA vPIC

Government

Built when you ask for it

Sync NHTSA vehicle identification and manufacturer data. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The NHTSA connector syncs vehicle product information into analytics-ready tables in your data warehouse. Pull VIN decodes, makes, models, manufacturers, plant records, and equipment from the NHTSA vPIC API, with Ingest handling pagination and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • VIN decoding
  • Makes and models
  • Manufacturers
  • Plants and equipment

How it gets built

  1. Choose NHTSA vPIC when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads NHTSA vPIC's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against NHTSA vPIC itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

None. The vPIC API is public and needs no credential.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a NHTSA vPIC connector?
Not as a finished connector yet. Ingest builds it from NHTSA vPIC's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can NHTSA vPIC data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

NHTSA vPIC API documentation: https://vpic.nhtsa.dot.gov/api/

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for government teams: Abilene TX 311, Albany NY 311, Ann Arbor MI 311, Anne Arundel County MD 311, Auburn WA 311, Aurora IL 311.

Request NHTSA vPIC