NHTSA vPIC Canadian Vehicle Dimensions
Use the NHTSA vPIC Canadian Vehicle Dimensions API to retrieve Canadian vehicle dimension specifications used in collision investigation and reconstruction. Provide a year from 1971 onward and the make, optionally narrowing by model and choosing Metric or US units and request JSON output. The response contains the available vehicle dimensions, weights and specification references. Use the results to support dimension comparisons, organize reconstruction reference data, or enrich a vehicle specification catalog. The dataset concerns vehicle measurements and should not be treated as a complete ownership or maintenance history. The detail page provides supported parameters, request and response examples, coverage notes, and the configured per-call price.
- Selected price
- $0.001 / callPublished pricing
- Sellers / implementations
- 1 / 1
- Requests · 30d
- —Loading...
- Success rate · 30d
- —Loading...
| Seller | Pricing | Requests · 30d | Performance | Access |
|---|---|---|---|---|
nhtsa-vpicCurrent NHTSA vPIC Canadian Vehicle Dimensions · GET · View API reference | $0.001 / call | — | —successP50— |
Run sends a real API request. Charges follow the published API contract.
Response structure
CountintegerMessagestringResultsobject[]Specsobject[]NamestringValuestring
SearchCriteriastring
// Inferred from response examples. Fields are optional and other fields may be returned.
export type ApiResponse = {
Count?: number;
Message?: string;
Results?: Array<{
Specs?: Array<{
Name?: string;
Value?: string;
}>;
}>;
SearchCriteria?: string;
};- Method
- GET
- Endpoint
https://api.openany.si/v1/agent-apis/nhtsa-vpic/api/vehicles/GetCanadianVehicleSpecifications- Content type
- application/json
- Authentication
Authorization: Bearer $OPENANY_API_KEY
curl \
'https://api.openany.si/v1/agent-apis/nhtsa-vpic/api/vehicles/GetCanadianVehicleSpecifications?format=json&make=Acura&model=MDX&units=Metric&year=2011' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'Input parameters
Fields in this listing; additional options and input encoding can vary by provider.
| Parameter | Location | Type | Required | Description |
|---|---|---|---|---|
year | URL query parametersquery | integer | Yes | Specification year, 1971 or later. minimum: 1971 |
make | URL query parametersquery | string | Yes | Vehicle make, such as Acura or Honda. minLength: 1 · maxLength: 200 |
model | URL query parametersquery | string | No | Optional model or additional specification descriptor. minLength: 1 · maxLength: 200 |
units | URL query parametersquery | string | No | Measurement units. Metric and US were both tested and produced converted values. The response uses Results[].Specs[] name/value entries, not flat dimension keys. enum: "Metric", "US" |
format | URL query parametersquery | string | Yes | Required output format for this OpenAny product. Use json; XML and CSV are not exposed by this configuration. enum: "json" |
Required markers inside a nested object or variant apply when that object or variant is used.
Sample response
Sample response · Documented HTTP 200 Example from the provider's documentation. Field values in your results will differ.
{
"Count": 1,
"Message": "Results returned successfully",
"Results": [
{
"Specs": [
{
"Name": "Make",
"Value": "ACURA"
},
{
"Name": "Model",
"Value": "MDX 4DR SUV AWD /TECH/ELITE"
},
{
"Name": "MYR",
"Value": "10"
},
{
"Name": "OL",
"Value": "485"
},
{
"Name": "OW",
"Value": "199"
},
{
"Name": "OH",
"Value": "173"
},
{
"Name": "WB",
"Value": "275"
},
{
"Name": "CW",
"Value": "2064"
},
{
"Name": "A",
"Value": "117"
},
{
"Name": "B",
"Value": "183"
},
{
"Name": "C",
"Value": "42"
},
{
"Name": "D",
"Value": "85"
},
{
"Name": "E",
"Value": "126"
},
{
"Name": "F",
"Value": "100"
},
{
"Name": "G",
"Value": "110"
},
{
"Name": "TWF",
"Value": "172"
},
{
"Name": "TWR",
"Value": "172"
},
{
"Name": "WD",
"Value": "56/44"
}
]
}
],
"SearchCriteria": "Year: 2011; Make: Acura; Model: MDX; Units: Metric"
}Agent integration
Copy the resource contract without sharing an API key.
View API Markdown
# NHTSA vPIC Canadian Vehicle Dimensions
Use the NHTSA vPIC Canadian Vehicle Dimensions API to retrieve Canadian vehicle dimension specifications used in collision investigation and reconstruction. Provide a year from 1971 onward and the make, optionally narrowing by model and choosing Metric or US units and request JSON output. The response contains the available vehicle dimensions, weights and specification references. Use the results to support dimension comparisons, organize reconstruction reference data, or enrich a vehicle specification catalog. The dataset concerns vehicle measurements and should not be treated as a complete ownership or maintenance history. The detail page provides supported parameters, request and response examples, coverage notes, and the configured per-call price.
Documentation: https://openany.si/apis/890884a8-4159-415b-914e-6fc3e87b4d8c
Method: GET
Endpoint: https://api.openany.si/v1/agent-apis/nhtsa-vpic/api/vehicles/GetCanadianVehicleSpecifications
Price: $0.001 / call
Provider: nhtsa-vpic
Contract revision: 1
Price source: OpenAny public API contract and documented provider unit rates. Price update time: not supplied.
Use OPENANY_API_KEY from the environment. API Key calls use your shared balance.
## Prepared request
```bash
curl \
'https://api.openany.si/v1/agent-apis/nhtsa-vpic/api/vehicles/GetCanadianVehicleSpecifications?format=json&make=Acura&model=MDX&units=Metric&year=2011' \
-X GET \
-H "Authorization: Bearer $OPENANY_API_KEY" \
-H 'Content-Type: application/json'
```
## API contract
```json
{
"resource_type": "api",
"name": "NHTSA vPIC Canadian Vehicle Dimensions",
"endpoint": "https://api.openany.si/v1/agent-apis/nhtsa-vpic/api/vehicles/GetCanadianVehicleSpecifications",
"method": "GET",
"content_type": "none",
"execution_mode": "sync",
"authentication": {
"type": "bearer",
"environment_variable": "OPENANY_API_KEY"
},
"inputs": [
{
"description": "Specification year, 1971 or later.",
"location": "query",
"minimum": "1971",
"name": "year",
"nullable": false,
"required": true,
"type": "integer"
},
{
"description": "Vehicle make, such as Acura or Honda.",
"location": "query",
"max_length": 200,
"min_length": 1,
"name": "make",
"nullable": false,
"required": true,
"type": "string"
},
{
"description": "Optional model or additional specification descriptor.",
"location": "query",
"max_length": 200,
"min_length": 1,
"name": "model",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Measurement units. Metric and US were both tested and produced converted values. The response uses Results[].Specs[] name/value entries, not flat dimension keys.",
"enum_values": [
"Metric",
"US"
],
"location": "query",
"name": "units",
"nullable": false,
"required": false,
"type": "string"
},
{
"description": "Required output format for this OpenAny product. Use json; XML and CSV are not exposed by this configuration.",
"enum_values": [
"json"
],
"location": "query",
"name": "format",
"nullable": false,
"required": true,
"type": "string"
}
],
"billing": {
"currency": "USD",
"mode": "fixed",
"priceMicroUsd": "1000",
"rounding": null,
"unit": "call",
"unitQuantity": null
},
"examples": [
{
"http_status": 200,
"name": "Official example · Verified live response",
"request": {
"body": null,
"headers": {},
"path": {},
"query": {
"format": "json",
"make": "Acura",
"model": "MDX",
"units": "Metric",
"year": 2011
}
},
"response_body": {
"Count": 1,
"Message": "Results returned successfully",
"Results": [
{
"Specs": [
{
"Name": "Make",
"Value": "ACURA"
},
{
"Name": "Model",
"Value": "MDX 4DR SUV AWD /TECH/ELITE"
},
{
"Name": "MYR",
"Value": "10"
},
{
"Name": "OL",
"Value": "485"
},
{
"Name": "OW",
"Value": "199"
},
{
"Name": "OH",
"Value": "173"
},
{
"Name": "WB",
"Value": "275"
},
{
"Name": "CW",
"Value": "2064"
},
{
"Name": "A",
"Value": "117"
},
{
"Name": "B",
"Value": "183"
},
{
"Name": "C",
"Value": "42"
},
{
"Name": "D",
"Value": "85"
},
{
"Name": "E",
"Value": "126"
},
{
"Name": "F",
"Value": "100"
},
{
"Name": "G",
"Value": "110"
},
{
"Name": "TWF",
"Value": "172"
},
{
"Name": "TWR",
"Value": "172"
},
{
"Name": "WD",
"Value": "56/44"
}
]
}
],
"SearchCriteria": "Year: 2011; Make: Acura; Model: MDX; Units: Metric"
}
},
{
"http_status": 200,
"name": "Official example · Verified US measurement units",
"request": {
"body": null,
"headers": {},
"path": {},
"query": {
"format": "json",
"make": "Acura",
"model": "MDX",
"units": "US",
"year": "2011"
}
},
"response_body": {
"Count": 1,
"Message": "Results returned successfully",
"Results": [
{
"Specs": [
{
"Name": "Make",
"Value": "ACURA"
},
{
"Name": "Model",
"Value": "MDX 4DR SUV AWD /TECH/ELITE"
},
{
"Name": "MYR",
"Value": "10"
},
{
"Name": "OL",
"Value": "190.9449"
},
{
"Name": "OW",
"Value": "78.3465"
},
{
"Name": "OH",
"Value": "68.1102"
},
{
"Name": "WB",
"Value": "108.2677"
},
{
"Name": "CW",
"Value": "4550.3357"
},
{
"Name": "A",
"Value": "46.063"
},
{
"Name": "B",
"Value": "72.0472"
},
{
"Name": "C",
"Value": "16.5354"
},
{
"Name": "D",
"Value": "33.4646"
},
{
"Name": "E",
"Value": "49.6063"
},
{
"Name": "F",
"Value": "39.3701"
},
{
"Name": "G",
"Value": "43.3071"
},
{
"Name": "TWF",
"Value": "67.7165"
},
{
"Name": "TWR",
"Value": "67.7165"
},
{
"Name": "WD",
"Value": "56/44"
}
]
}
],
"SearchCriteria": "Year: 2011; Make: Acura; Model: MDX; Units: US"
}
}
]
}
```Error handling
| Status | Next step |
|---|---|
400 | Check the offering and request fields. |
401 / 403 | Verify your credentials and access permissions. |
402 | Inspect the selected access mode and returned payment requirements. |
429 | Respect the returned rate limit and retry guidance. |
5xx | Inspect the error and usage record before retrying a paid operation. |
Official example · Verified live response
Example from the provider's documentation. Field values in your results will differ.
Prepare your environment
Use a terminal with cURL installed.
Use an OpenAny API key with shared-balance access. Confirm availability and price before running; a call may charge your balance.
Set the key in your terminal using the hidden prompt below. Keep its value out of source files and logs.
Terminal · macOS / Linuxprintf 'OpenAny API key: ' read -r -s OPENANY_API_KEY export OPENANY_API_KEY printf '\n'Run the request
Paste the complete command below into your terminal.
Values to replace before running 5
Review these request fields before running. Keep the published provider and request method unchanged.
year- Specification year, 1971 or later.
make- Vehicle make, such as Acura or Honda.
model- Optional model or additional specification descriptor.
units- Measurement units. Metric and US were both tested and produced converted values. The response uses Results[].Specs[] name/value entries, not flat dimension keys.
format- Required output format for this OpenAny product. Use json; XML and CSV are not exposed by this configuration.
Terminal · cURLcurl \ 'https://api.openany.si/v1/agent-apis/nhtsa-vpic/api/vehicles/GetCanadianVehicleSpecifications?format=json&make=Acura&model=MDX&units=Metric&year=2011' \ -X GET \ -H "Authorization: Bearer $OPENANY_API_KEY" \ -H 'Content-Type: application/json'Check the response
Sample response · Documented HTTP 200
Sample response{ "Count": 1, "Message": "Results returned successfully", "Results": [ { "Specs": [ { "Name": "Make", "Value": "ACURA" }, { "Name": "Model", "Value": "MDX 4DR SUV AWD /TECH/ELITE" }, { "Name": "MYR", "Value": "10" }, { "Name": "OL", "Value": "485" }, { "Name": "OW", "Value": "199" }, { "Name": "OH", "Value": "173" }, { "Name": "WB", "Value": "275" }, { "Name": "CW", "Value": "2064" }, { "Name": "A", "Value": "117" }, { "Name": "B", "Value": "183" }, { "Name": "C", "Value": "42" }, { "Name": "D", "Value": "85" }, { "Name": "E", "Value": "126" }, { "Name": "F", "Value": "100" }, { "Name": "G", "Value": "110" }, { "Name": "TWF", "Value": "172" }, { "Name": "TWR", "Value": "172" }, { "Name": "WD", "Value": "56/44" } ] } ], "SearchCriteria": "Year: 2011; Make: Acura; Model: MDX; Units: Metric" }
Loading related APIs…
Common questions
Do I need a separate key for every provider?
Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.
Are these providers interchangeable?
No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.
How is this API billed?
API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.
Where do the price and contract come from?
The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.
How do OpenAny Balance and x402 differ?
OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.
Does Playground send a paid request?
Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.
Use NHTSA vPIC Canadian Vehicle Dimensions with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.