/fmcsa/carriers

POST /api/fmcsa/carriers

Price: 1 credit

Get a motor carrier's FMCSA registration record by USDOT number: legal and DBA names, USDOT status, contacts, company officers, addresses, MCS-150 figures, and operating authorities with their insurance and blanket filings.

How to use it

Use this for a carrier's current registration, contacts and operating authority (MC docket) status. Find a USDOT number by name with fmcsa/carriers/search; inspection, crash and safety-rating figures come from fmcsa/carriers/snapshots.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• usdot string required — USDOT number of the carrier (examples: "54283", "2454645"; minLength: 1)

Response

• @type string (default: "FmcsaCarrier")
• usdot string required
• url string required
• name string nullable
• dba_names array (default: [])
• usdot_suffix string nullable
• usdot_status string nullable
• is_out_of_service boolean nullable
• phmsa_number string nullable
• entity_types array (default: [])
• business_type string nullable
• business_type_other string nullable
• emails array (default: [])
• phones array (default: [])
• addresses array (default: [])
  • @type string (default: "FmcsaAddress")
  • address_type string nullable
  • street string nullable
  • street2 string nullable
  • city string nullable
  • state string nullable
  • zip_code string nullable
  • zip_code_extension string nullable
  • county string nullable
  • colonia string nullable
  • country string nullable
• officers array (default: [])
  • @type string (default: "FmcsaCarrierOfficer")
  • name string required
  • first_name string nullable
  • middle_name string nullable
  • last_name string nullable
  • suffix string nullable
  • phone string nullable
  • email string nullable
• duns string nullable
• oic_state string nullable
• state_of_incorporation string nullable
• year_of_incorporation integer nullable
• gross_revenue number nullable
• mcs150_filed_at integer nullable
• mcs150_mileage integer nullable
• mcs150_mileage_year integer nullable
• recent_mileage integer nullable
• recent_mileage_year integer nullable
• biennial_update_due_at integer nullable
• revoked_at integer nullable
• suspended_at integer nullable
• driver_count integer nullable
• interstate_driver_count integer nullable
• power_unit_count integer nullable
• straight_truck_count integer nullable
• average_power_units number nullable
• registrations array (default: [])
  • @type string (default: "FmcsaRegistration")
  • registrant_type string nullable
  • operations array (default: [])
  • is_mexico_owned boolean nullable
  • is_in_protest_period boolean nullable
  • minimum_coverage_amount number nullable
  • bipd_on_file_amount number nullable
  • cargo_required_amount number nullable
  • cargo_on_file_amount number nullable
  • bond_required_amount number nullable
  • bond_on_file_amount number nullable
  • common_authority_status string nullable
  • contract_authority_status string nullable
  • broker_authority_status string nullable
  • common_application_pending string nullable
  • contract_application_pending string nullable
  • broker_application_pending string nullable
  • common_revocation_pending string nullable
  • contract_revocation_pending string nullable
  • broker_revocation_pending string nullable
  • registration_number string nullable
  • prefix string nullable
  • cd_number string nullable
  • mx_type string nullable
  • fhwa_region string nullable
  • operating_authorities array (default: [])
    • @type string (default: "FmcsaOperatingAuthority")
    • docket_number string required
    • authority_type string nullable
    • status string nullable
    • protest_period_started_at integer nullable
    • insurance_filings array (default: [])
    • blanket_filings array (default: [])

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 — No carrier is registered under this USDOT number 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.