How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
US Department of Transportation

US Department of Transportation vehicles API

Vehicle search and list endpoints

Documentation Provider Profile APIs.io OpenAPI GitHub

US Department of Transportation vehicles API is one of 12 APIs that US Department of Transportation publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Vehicles. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 17 operations across 17 paths, and defines 24 schemas. It is described by OpenAPI 2.0, at version 1.6.0.

Requests are made against the base URL https://mobile.fmcsa.dot.gov/qc/services.

17 operations 17 paths 24 schemas 17 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1.6.0
Base URL
https://mobile.fmcsa.dot.gov/qc/services
Resource Areas
1

Paths & Operations 17

Across 17 paths, the API surfaces 17 operations — 17 GET. Each is listed below with its method, path, parameters, and response codes.

vehicles 17

Vehicle search and list endpoints

GET
/vehicles
4 params → 200400500
GET
/vehicles/byArtemisId
3 params → 200400500
GET
/vehicles/byMultipleArtemisIds
3 params → 200400500
GET
/vehicles/byClass
5 params → 200400500
GET
/vehicles/byIds
5 params → 200400500
GET
/vehicles/byManufacturer
11 params → 200400500
GET
/vehicles/byNcapId
5 params → 200400500
GET
/vehicles/bySearch
12 params → 200400500
GET
/vehicles/byVin
3 params → 200400500
GET
/vehicles/byYmmt
9 params → 200400500
GET
/vehicles/classes
2 params → 200500
GET
/vehicles/makes
4 params → 200400500
GET
/vehicles/manufacturers
3 params → 200400500
GET
/vehicles/modelYears
2 params → 200400500
GET
/vehicles/models
5 params → 200400500
GET
/vehicles/trims
5 params → 200400500
GET
/vehicles/{id}/details
3 params → 200400500

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are VehicleDetails (17 properties), VehicleBasic (15 properties), ComplaintAggregate (12 properties), RecallAggregate (11 properties). Each schema is shown below with its type and property counts.

PartialVehicle
object
7 properties
VehicleBasicWrapped
object
2 properties
VehicleBasic
object
15 properties
PartialVehicleWrapped
object
2 properties
RecommendedFeature
object
8 properties
Investigations
object
2 properties
MFRCommunicationAggregate
object
6 properties
VehicleDetailsWrapped
object
2 properties
ComplaintAggregate
object
12 properties
CrashTestRating
object
10 properties
InvestigationAggregate
object
8 properties
RecallAggregate
object
11 properties
Recalls
object
2 properties
Message
object
4 properties
Feature
object
3 properties
VehicleDetails
object
17 properties
Components
object
1 property
Rating
object
8 properties
Media
object
2 properties
Pagination
object
9 properties
SafetyFeature
object
3 properties
SafetyRatingAggregate
object
3 properties
SafetyIssueAggregate
object
4 properties
Meta
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dot-vehicles-api-openapi.yml Raw ↑

Other APIs US Department of Transportation publishes across the network.

FMCSA QCMobile API
AE Profile APIs.io
FMCSA SaferBus API
AE Profile APIs.io
NHTSA vPIC Vehicle API
AE Profile APIs.io
NHTSA Datasets and APIs
AE Profile APIs.io
DOT Open Data Portal
AE Profile APIs.io
US Department of Transportation childSeats API
AE Profile APIs.io
US Department of Transportation equipment API
AE Profile APIs.io
US Department of Transportation ewr API
AE Profile APIs.io
US Department of Transportation foreignCampaigns API
AE Profile APIs.io
US Department of Transportation safetyIssues API
AE Profile APIs.io
US Department of Transportation tires API
AE Profile APIs.io
#Vehicles
← Back to U APIs
API Details
ID
dot:dot-vehicles-api
Base URL
https://mobile.fmcsa.dot.gov/qc/services
Docs
https://mobile.fmcsa.dot.gov/QCDevsite/docs/qcApi
Provider
US Department of Transportation
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=dot-vehicles-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/dot-vehicles-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of US Department of Transportation vehicles API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.