/nhtsa/manufacturers/search

POST /api/nhtsa/manufacturers/search

Price: 10 credits

List vehicle manufacturers registered with NHTSA, optionally of one manufacturer type.

How to use it

Use it to browse or export the register of vehicle manufacturers, for example every vehicle alterer. Rows carry name, country and vehicle types; pass an `id` to nhtsa/manufacturers for address and contacts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• manufacturer_type string nullable — Keep manufacturers whose type name contains this text (examples: "alterer"; minLength: 1)
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "NhtsaManufacturer")
• id string required
• name string nullable
• common_name string nullable
• country string nullable
• vehicle_types array (default: [])
  • @type string (default: "NhtsaManufacturerVehicleType")
  • name string nullable
  • is_primary boolean nullable
  • gvwr_from string nullable
  • gvwr_to string nullable
• manufacturer_types array (default: [])
• dba_names string nullable
• address string nullable
• address2 string nullable
• city string nullable
• state_province string nullable
• postal_code string nullable
• contact_email string nullable
• contact_phone string nullable
• contact_fax string nullable
• principal_first_name string nullable
• principal_last_name string nullable
• principal_position string nullable
• primary_product string nullable
• other_details string nullable
• submitted_by_name string nullable
• submitted_by_position string nullable
• submitted_at string nullable
• updated_at 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.