--- title: "Cars - Returns tracing details for railcars on the BNSF network, with a default page size of 2,000." method: GET path: "/v1/cars" tags: ["CARLOAD"] --- # Cars - Returns tracing details for railcars on the BNSF network, with a default page size of 2,000. `GET /v1/cars` ## Request - Base URL: `https://api.bnsf.com:6443` - URL: `https://api.bnsf.com:6443/v1/cars` - Auth: none declared - TypeScript: (a function with typed inputs; its response is checked against the schema) ## Query parameters - `limit` integer - `page` integer ## Response `200` **OK** The request has succeeded. - object - `elements` Carload[] - `destinationRailNetworkLocationName` string: The final BNSF operating station and state. This can be different than customer destination. See **rail_destination_station_state** the final rail station and state as stated on the waybill. - `equipmentInitial` string: The initials used in the equipment identification for the shipment. - `equipmentNumber` string: The numbers used in the equipment identification for the shipment. - `equipmentLoadStatusCode` 'L' | 'E': L or E, this code describes whether the equipment is loaded or empty - `estimatedShipmentAvailabilityDate` string: Estimated date that the shipment becomes available to the customer - `estimatedShipmentAvailabilityTime` string: Estimated time that the shipment becomes available to the customer - `finalDestinationRailNetworkLocationName` string: The final station and state as stated on the waybill. - `finalScheduledEventDescription` string: Description of the final scheduled event in the trip plan - `lastEventDate` string: Date of most recent event. - `lastEventDescription` string: Description of most recent event - `lastEventTime` string: Time of most recent event. - `lastEventRailNetworkLocationName` string: The location of the most recently reported event. See Event Description. - `lastReportingSCAC` string: Carrier abbreviation reporting the most recent event. - `latitude` number, float: Last reported latitude of the shipment. - `longitude` number, float: Last reported longitude of the shipment. - `message` string: Message regarding equipment search - `nextSCAC` string: The next carrier to move the shipment after BNSF. - `nextScheduledEventDate` string: The estimated date the next scheduled event will occur. - `nextScheduledEventDescription` string: The next scheduled event to occur in the trip plan. - `nextScheduledEventStateCode` string: The state where the next scheduled event will occur. - `nextScheduledEventStation333` string: The station where the next scheduled event will occur. - `nextScheduledEventTime` string: The estimated time the next scheduled event will occur. - `originRailNetworkLocationName` string: The origin station and state of the shipment. - `shipmentExceptionDescription` string: A description of any exception that applies to the shipment - `trainId` string: The code that identifies a specific train and is used to locate cars, units, or shipments. Train IDs consist of four parts: Type: Train type, based on the commodity being transported, or the speed the train needs to move. Valid values range from A to Z. Symbol: A combination of carrier interchange and the number of trains out that day. Day: The day of the month the train departed from origin location, in mm-dd format. Schedule ID: A value from A to Z. - `waybillNumber` string: Waybill number assigned to the shipment. - `careOfParty633` string: Name of a receiver of rail cars on behalf of the actual consignee (the physical delivery point) which has been abbreviated from the Customer's full Legal Name through the use of a standardized programmatic process. - `careOfPartyFullName` string: The full name of a receiver of rail cars on behalf of the actual consignee (the physical delivery point). - `consignee633` string: Name of a Customer, acting as the Consignee (AKA Receiver), which has been abbreviated from the Customer's full Legal Name through the use of a standardized programmatic process. - `consigneeFullName` string: The full name of a customer that is filling the role of Consignee. A Consignee, also referred to as the \"Receiver\", is the company or individual receiving a shipment at a destination. - `notifyParty633` string: Name of the party to be notified at the time a container or trailer is grounded from a train. Most notify parties are draymen. Value has been abbreviated from the Customer's full Legal Name through the use of a standardized programmatic process. - `notifyPartyFullName` string: Full name of the party to be notified at the time a container or trailer is grounded from a train. Most notify parties are draymen. - `shipper633` string: Name of a Customer, acting as the Shipper, which has been abbreviated from the Customer's full Legal Name through the use of a standardized programmatic process. - `shipperFullName` string: Full name of a Customer, acting as the Shipper. - `stcc` string: STCC (Standard Transportation Commodity Code) number identifying a Commodity. - `billOfLadingId` string: Is a unique identifier for an instance of an internal or external customer request for the Bill of Lading via rail. ## Other responses - `400`: **Bad Request** The request could not be understood by the server due to incorrect syntax. Do not repeat the request without modifications. - `403`: Unauthorized request. Here are the most common causes: * You are getting 403 Access Denied. * It takes a few days for us to get you set up after you register. When set up is complete, you will receive an email letting you know. If you have not received the email, please wait up to five business days. Let us know via API Support if you still have not received the email after five business days. * You can also get this error if your certificate is not configured properly on your side. Please review the Mutual Authentication in the Getting Started section of our documentation. * You are getting 403 "message": "Insufficient privileges" when accessing a restricted service for which you do not have permission. You can use our Registration form to request access. Be sure to explain the situation in the "Please explain how you intend to use the API" field. - `404`: **Not Found** The server cannot find the requested resource (URI). That is, the address of the endpoint in your request does not exist. Please consult the documentation. - `405`: **Method Not Allowed** The request HTTP method is known by the server but has been disabled and cannot be used for that resource. For example, you may be using GET when POST is required. Please consult the documentation. - `429`: **Too Many Requests** The BNSF API Gateway enforces rate limits to maintain application security and performance. Current rate limits are set as follows: * 1 API Request Per Second, Per Partner, Per Service * 15 API Requests Per Minute, Per Partner, Per Service * 100 API Request Per Minute, Per Service When requests exceed these limits the API Gateway will return a **429 Too Many Requests** error response. Upon receiving such exceptions, you can resubmit failed requests in a rate-limited manner, complying with the API Gateway throttle limits. - `500`: **Internal Server Error** The server encountered an unexpected condition which prevented it from fulfilling the request. This is always a problem on the server side. Our internal support systems will be made aware. - `504`: **Gateway Timeout** The server is acting as a gateway and cannot get a response in time for a request. Wait about one minute then try again. --- [API](https://skmtc.dev/bnsf/apis/bnsf-trace-api.md) - [All operations](https://skmtc.dev/bnsf/apis/bnsf-trace-api/llms.txt) - [OpenAPI document](https://skmtc.dev/bnsf/apis/bnsf-trace-api/revisions/777129ca823f?raw)