/nhtsa/canada-specs/search

POST /api/nhtsa/canada-specs/search

Price: 10 credits

List Canadian vehicle dimension sheets for a make and model year: overall length, width and height, wheelbase, curb weight, track widths and weight distribution per model variant.

How to use it

Use it to compare the size and weight of model variants, for example to check garage or trailer fit. Each row is one body and trim variant named in `model`; `weight_distribution` is the front/rear split in percent.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• model_year integer required — Model year (examples: 2020; min: 1900; max: 2100)
• make string required — Vehicle make (examples: "toyota"; minLength: 1)
• model string nullable — Keep models whose name contains this text (examples: "camry"; minLength: 1)
• units string required — metric for centimetres and kilograms, us for inches and pounds (one of: "metric", "us"; examples: "metric")
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "NhtsaCanadaSpec")
• make string nullable
• model string nullable
• model_year integer nullable
• units string nullable (one of: "metric", "us")
• myr string nullable
• overall_length number nullable
• overall_width number nullable
• overall_height number nullable
• wheelbase number nullable
• curb_weight number nullable
• dimension_a number nullable
• dimension_b number nullable
• dimension_c number nullable
• dimension_d number nullable
• dimension_e number nullable
• dimension_f number nullable
• dimension_g number nullable
• track_width_front number nullable
• track_width_rear number nullable
• weight_distribution string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.