API V4 – Search by Docket Number

The /v4/search/docket/ endpoint lets you load the list of carriers that have been associated with any particular MC/FF/MX number.

The key distinction between this endpoint and /v4/search/dot/ is that this endpoint returns a list of carriers, not an in-depth profile, even if only one carrier matches to the MC/FF/MX number.

Notes on this endpoint:

  1. Authentication via header. To authenticate your API call, pass in your public API key with the X-Api-Key HTTP header.

HTTP Request

Method URL
GET https://api.brokercarrier.com/v4/search/docket

Required Parameters

Name Type Value(s)
docket_number string Any known MC/FF/MX number

Example Response

Request: https://api.brokercarrier.com/v4/search/docket?docket_number=456807

The example response below shows the public overview data of a carrier whose docket numbers included 456807 in the previous five years.

{
    "prefix": "MC",
    "carriers": [
        {
            "dot_number": "1112473",
            "authority": [
                {
                    "status": {
                        "broker": "a",
                        "common": "a",
                        "contract": "a"
                    },
                    "authorized": {
                        "hhg": "n",
                        "broker": "y",
                        "property": "y",
                        "passenger": "n"
                    },
                    "docket_number": 456807,
                    "docket_prefix": "MC"
                }
            ],
            "docket_numbers": [
                {
                    "docket_number": 456807,
                    "docket_prefix": "MC"
                }
            ],
            "legal_name": "LOAD ONE LLC",
            "carrier_operation": "A",
            "phy_address": "13221 INKSTER RD TAYLOR, MI 48180",
            "mailing_address": "13221 INKSTER RD TAYLOR, MI 48180",
            "email": "jschmalz@load1.com",
            "phone": "(800) 957-4698",
            "active": "y",
            "onboarded": {
                "status": 0
            }
        }
    ]
}