---
title: "VIN Details - Returns detailed information about your VIN shipments."
method: GET
path: "/v1/vin-details"
tags: ["AUTOMOTIVE"]
---

# VIN Details - Returns detailed information about your VIN shipments.

`GET /v1/vin-details`

## Request

- Base URL: `https://api.bnsf.com:6443`
- URL: `https://api.bnsf.com:6443/v1/vin-details`
- Auth: none declared
- TypeScript: <https://skmtc.dev/bnsf/apis/bnsf-trace-api/docs/v1/vin-details/get.ts> (a function with typed inputs; its response is checked against the schema)

## Query parameters

- `vinList` string

## Response `200`

**OK**

The request has succeeded.

- VinDetails: Vin Details
  - `jobStatus` integer
  - `jobStatusDescription` string
  - `resultSet` object[]
    - `asnCreatedIndicator` string: Indicates whether an ASN (Advanced Shipping Notice) was created for a shipment or not.
    - `autorackDeckPositionNumber` string: The position where a vehicle is placed in the autorack deck.
    - `autorackOnSpotIndicator` string: Indicates whether the autorack is on spot or actually placed for unloading.
    - `autorackTypeDescription` string: Type of autorack.
    - `billOfLadingId` string: Unique identifier for an instance of an internal or external customer request for the shipment of lading via rail.
    - `carInitial` string: Initials, also known as reporting marks, assigned to a piece of railroad equipment by the equipment's owner. Value is used with Car Number to uniquely identify a piece of equipment.
    - `carNumber` string: Number assigned to a piece of on rail railroad equipment by the equipment's owner. Value is used with Car Initials to uniquely identify a piece of equipment.
    - `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.
    - `customerNotifiedDatetime` string: Date and time a BNSF customer was notified about their shipment.
    - `destinationWaybillLocationName` string: Standard abbreviation of the city and the state code of the location that is defined as the destination of a shipment in the Waybill.
    - `estimatedShipmentAvailabilityDatetime` string: The date and time when a shipment will be available for the consignee to pick it up.
    - `haulawayCompanyName` string: The name of the company to which a haulaway belongs to.
    - `haulawayScac` string: The SCAC (Standard Carrier Alpha Code) of a haulaway.
    - `inventoryYardCheckDatetime` string: Date and time when the yard check to maintain the inventory of which shipments are in the hub and where took place.
    - `ladingRampRailNetworkLocationName` string: Standard abbreviation of the city and the state code of the rail network location where a lading was ramped.
    - `lastEventDatetime` string: Date and time of the last event recorded.
    - `lastEventDescription` string: Description of the last event recorded.
    - `lastEventRailNetworkLocationName` string: Standard abbreviation of the city and the state code of the rail network location where the last reported event occurred.
    - `latitude ` string: Last reported latitude of the shipment.
    - `longitude` string: Last reported longitude of the shipment.
    - `newVehicleIndicator` string: Indicates whether the vehicle is new or not.
    - `nextScheduledEventDate` string: The date when the next scheduled event will take place.
    - `nextScheduledEventDescription` string: Description of the next scheduled event.
    - `nextScheduledEventStation333` string: Name of the city where the next scheduled event will occur. This name has been abbreviated from the city's full name through the use of a standardized programmatic algorithm.
    - `nextScheduledEventStationStateCode` string: The state code for a station where the next scheduled event will occur.
    - `nextScheduledEventTime` string: The date when the next scheduled event will take place.
    - `originWaybillLocationName` string: Standard abbreviation of the city and the state code of the location that is defined as the origin of a shipment in the Waybill.
    - `outgateDatetime` string: The date when the outgate took place.
    - `parkingLotZoneBayCode` string: Code of the bay used along with the zone to locate the spot in the parking lot where shipments are unloaded from the railcar.
    - `parkingLotZoneCode` string: Code to locate the zone in a parking lot where shipments are unloaded from the railcar.
    - `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.
    - `stcc` string: STCC (Standard Transportation Commodity Code) number identifying a Commodity.
    - `trainId` string: The identification of an train. (The composite of the type, symbol, section, day, and priority.)
    - `vehicleBodyClassName` string: The body style of a vehicle that informs its shape, number of doors, and mechanical setup.
    - `vehicleDealerAddress` string: The address of a vehicle dealer.
    - `vehicleDealerCode` string: Vehicle Dealer Code is assigned by a vehicle manufacturer as a way to identify a dealer that they conduct business with.
    - `vehicleInspectionDamageFoundIndicator` string: Indicates whether damage was found during the inspection of a vehicle that was transported by BNSF.
    - `vehicleMakeName` string: The car manufacturer who makes the vehicle or the vehicle's brand.
    - `vehicleModelName` string: The design of a vehicle, in the context of the manufacturer's range or series of vehicles.
    - `vehiclePreBayDatetime` string: Date and time when a vehicle was assigned the zone and bay information where it will be placed in the parking lot after being unloaded from the railcar.
    - `vehicleUnloadedDatetime` string: Date and time when a vehicle was unloaded from the railcar.
    - `vin` string: A vehicle identification number (VIN) (also called a chassis number or frame number) is a unique code, including a serial number, used by the automotive industry to identify individual motor vehicles, towed vehicles, motorcycles, scooters and mopeds, as defined in ISO 3779 (content and structure) and ISO 4030 (location and attachment).
    - `waybillDate` string: Waybill Date is the day, month, and year specified on a waybill. Value can not be a future date.
    - `waybillNumber` string: Waybill Number is the carrier accounting number of a waybill.
  - `rowCount` string

## 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)
