FMCSA Carrier Vetting API

API ID 14343

Check US motor carriers against live FMCSA records: operating status, authority, safety rating, crash and inspection summary, plus a load vet pack combining authority, SMS BASICs, broker authority and an OFAC name screen.

API Documentation

Endpoints

Request
Returns the live FMCSA record for a US motor carrier by USDOT or MC number: legal name, operating status, authority, safety rating, fleet size, crashes and plain flags.
Endpoint ID: 35949
GET https://zylalabs.com/api/14343/fmcsa+carrier+vetting+api/35949/check+carrier+authority
INPUT PARAMETERS

Check Carrier Authority — Endpoint Features

Object Description
dot Optional Carrier USDOT number (give dot or mc).
mc Optional Carrier MC/docket number, e.g. MC-121058 (give dot or mc).

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

dot
mc
API EXAMPLE RESPONSE
JSON
{
    "order_id": "ord_example_c1",
    "sku": "carrier-authority-check",
    "status": "DELIVERED",
    "delivery": {
        "query": {
            "dot": "44110",
            "mc": null
        },
        "found": true,
        "carrier": {
            "legal_name": "GREYHOUND LINES INC",
            "dba_name": "BOLT BUS",
            "dot": 44110,
            "ein_present": true,
            "phy_city": "DALLAS",
            "phy_state": "TX",
            "allowed_to_operate": "Y",
            "status_code": "A",
            "oos_date": null
        },
        "authority": {
            "common": "A",
            "contract": "A",
            "broker": "I"
        },
        "safety": {
            "rating": "S",
            "rating_date": "2026-07-08",
            "total_power_units": 683,
            "total_drivers": 905,
            "crash_total": 70,
            "fatal_crash": 6,
            "tow_crash": 25,
            "driver_insp": 766,
            "driver_oos_rate": 1.4360313315926894,
            "vehicle_insp": 336,
            "vehicle_oos_rate": 7.440476190476191
        },
        "flags": [],
        "verdict": "CLEAR",
        "source": "FMCSA QCMobile (US DOT, live)",
        "retrieved_at": "2026-10-18T21:34:36.295Z",
        "disclaimer": "Federal registration/safety data; verify insurance separately before tendering."
    },
    "channel": "zyla"
}
Check Carrier Authority — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14343/fmcsa+carrier+vetting+api/35949/check+carrier+authority?dot=44110' --header 'Authorization: Bearer YOUR_API_KEY' 


    
Request
Pre-tender check returning TENDER, HOLD or REJECT from FMCSA authority, SMS BASICs, broker authority and an optional OFAC name screen, with reasons and sources. A section that times out returns status "timeout" with partial:true and a HOLD verdict (never TENDER; a REJECT stays REJECT). Full price applies when carrier authority (broker, for a broker-only pack) is delivered; if that core section times out, or every section does, the call fails with 503 before payment settles.
Endpoint ID: 35950
GET https://zylalabs.com/api/14343/fmcsa+carrier+vetting+api/35950/vet+load
INPUT PARAMETERS

Vet Load — Endpoint Features

Object Description
dot Optional Carrier USDOT number (give dot, mc or broker_mc).
mc Optional Carrier MC/docket number (give dot, mc or broker_mc).
broker_mc Optional Broker MC/docket number to run the broker authority check.
name Optional Legal name to screen against OFAC lists.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

dot
mc
broker_mc
name
API EXAMPLE RESPONSE
JSON
{
    "order_id": "ord_example_lv1",
    "sku": "load-vet-pack",
    "status": "DELIVERED",
    "delivery": {
        "query": {
            "dot": "44110",
            "mc": null,
            "broker_mc": null,
            "name": null
        },
        "verdict": "HOLD",
        "reasons": [
            "ACUTE_CRITICAL_DRIVER_FITNESS"
        ],
        "partial": false,
        "sections": {
            "authority": "ok",
            "basics": "ok",
            "broker": "skipped",
            "ofac": "skipped"
        },
        "hold_basis": "carrier_risk",
        "authority": {
            "query": {
                "dot": "44110",
                "mc": null
            },
            "found": true,
            "carrier": {
                "legal_name": "GREYHOUND LINES INC",
                "dba_name": "BOLT BUS",
                "dot": 44110,
                "ein_present": true,
                "phy_city": "DALLAS",
                "phy_state": "TX",
                "allowed_to_operate": "Y",
                "status_code": "A",
                "oos_date": null
            },
            "authority": {
                "common": "A",
                "contract": "A",
                "broker": "I"
            },
            "safety": {
                "rating": "S",
                "rating_date": "2026-07-08",
                "total_power_units": 683,
                "total_drivers": 905,
                "crash_total": 70,
                "fatal_crash": 6,
                "tow_crash": 25,
                "driver_insp": 766,
                "driver_oos_rate": 1.4360313315926894,
                "vehicle_insp": 336,
                "vehicle_oos_rate": 7.440476190476191
            },
            "flags": [],
            "verdict": "CLEAR",
            "source": "FMCSA QCMobile (US DOT, live)",
            "retrieved_at": "2026-10-18T21:34:36.295Z",
            "disclaimer": "Federal registration/safety data; verify insurance separately before tendering."
        },
        "basics": {
            "query": {
                "dot": "44110"
            },
            "found": true,
            "carrier_group": "passenger",
            "basics": [
                {
                    "basic": "Unsafe Driving",
                    "percentile": 3,
                    "percentile_public": true,
                    "measure_value": 0.61,
                    "exceeded_intervention_threshold": false,
                    "acute_critical_violation": false,
                    "basic_alert": false,
                    "inspections_with_violation": 38
                },
                {
                    "basic": "Hours-of-Service Compliance",
                    "percentile": 49,
                    "percentile_public": true,
                    "measure_value": 0.12,
                    "exceeded_intervention_threshold": false,
                    "acute_critical_violation": false,
                    "basic_alert": false,
                    "inspections_with_violation": 41
                },
                {
                    "basic": "Driver Fitness",
                    "percentile": 57,
                    "percentile_public": true,
                    "measure_value": 0.07,
                    "exceeded_intervention_threshold": false,
                    "acute_critical_violation": true,
                    "basic_alert": true,
                    "inspections_with_violation": 7
                }
            ],
            "flags": [
                "ACUTE_CRITICAL_DRIVER_FITNESS"
            ],
            "data_quality_flags": [],
            "inspections_24m": 797,
            "driver_oos_inspections": 10,
            "vehicle_oos_inspections": 24,
            "verdict": "REVIEW",
            "as_of": "2026-10-13T07:05:22.000Z",
            "as_of_basis": "portal_publish_date",
            "stale": false,
            "source": "FMCSA SMS monthly results",
            "retrieved_at": "2026-10-18T21:34:36.295Z",
            "disclaimer": "Monthly FMCSA SMS snapshot. as_of_basis says whether as_of is the dataset snapshot date or the portal publish date. Property-carrier percentiles are not public. stale=true means the published data is old (data quality), not that the carrier is risky."
        },
        "broker": {
            "skipped": true,
            "reason": "no broker_mc given"
        },
        "ofac": {
            "skipped": true,
            "reason": "no legal name provided"
        },
        "sources": [
            {
                "name": "FMCSA QCMobile (US DOT, live)",
                "as_of": "2026-10-18T21:34:36.295Z"
            },
            {
                "name": "FMCSA SMS monthly results",
                "as_of": "2026-10-13T07:05:22.000Z"
            }
        ],
        "method": "public FMCSA registration/SMS fields and OFAC name list only; no fraud score",
        "disclaimer": "TENDER/HOLD/REJECT is a mechanical reading of public fields, not legal advice and not a risk model. Verify insurance and identity separately before tendering."
    },
    "channel": "zyla"
}
Vet Load — CODE SNIPPETS

curl --location --request GET 'https://zylalabs.com/api/14343/fmcsa+carrier+vetting+api/35950/vet+load?dot=44110' --header 'Authorization: Bearer YOUR_API_KEY' 


    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the FMCSA Carrier Vetting API simply include your bearer token in the Authorization header.

Headers
Header Description
Authorization Required Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

No long-term commitment. Upgrade, downgrade, or cancel anytime.

Starts at
$10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

Check US motor carriers against live FMCSA records: operating status, authority, safety rating, crash and inspection summary, plus a load vet pack combining authority, SMS BASICs, broker authority and an OFAC name screen.

FMCSA Carrier Vetting API FAQs

Live FMCSA QCMobile registration records and the monthly FMCSA Safety Measurement System (SMS) snapshot. Every response cites its sources and as_of dates.

Hold_basis says why: carrier_risk (for example an acute or critical violation) or data_quality (the published safety data is stale, not a finding against the carrier).

FMCSA does not publish property-carrier percentiles or threshold alerts, so freight carriers are flagged only on acute or critical violations.

No. Verify insurance and identity separately before tendering.

General FAQs

To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.

You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.

The free trial lasts for 7 days and allows you to make up to 50 API requests.

No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.

Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

You can monitor your API usage through the response headers included with every request:

x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.

Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs