---
title: "IP Trains - Provides current status, with tracing details up to 25 industrial products unit trains."
method: POST
path: "/v1/ip-trains"
tags: ["TRAINS"]
---

# IP Trains - Provides current status, with tracing details up to 25 industrial products unit trains.

`POST /v1/ip-trains`

## Request

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

## Request body

- object
  - `trainList` string[]

## Response `200`

**OK**

The request has succeeded.

- object
  - `elements` Ag[]
    - `destinationRailNetworkLocationName` string: The final BNSF operating station and state. This can be different than customer destination. See **finalDestinationRailNetworkLocationName** the final rail station and state as stated on the waybill.
    - `emptyCarCount` integer: Number of empty cars on the train
    - `estimatedShipmentAvailabilityDateTime` string: Estimated date and time that the shipment becomes available to the customer
    - `lastEventDateTime` string
    - `lastEventDescription` string: Description of most recent event
    - `lastEventRailNetworkLocationName` string: The location of the most recently reported event. See Event Description.
    - `latitude` number, float: Last reported latitude of the shipment.
    - `loadedCarCount` integer: Number of loaded cars on the train
    - `longitude` number, float: Last reported longitude of the shipment.
    - `nextTrainId` string: Next train ID
    - `originRailNetworkLocationName` string: The origin station and state of the shipment.
    - `shuttleTrainPermitNumber` string: Shuttle train permint number
    - `shuttleOperatorCompanyAbbreviation` string: Shuttle current trip operator customer abbreviation
    - `shuttleOrderRequesterAbbreviation` string: Shuttle order requester customer abbreviation
    - `shuttleOwnerCompanyAbbreviation` string: Shuttle owner customer abbreviation
    - `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.

## 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.
- `413`: **Payload Too Large** The request entity is larger than limits defined by server.
- `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 **429 Too Many Requests** error response to the Client. Upon receiving such exceptions, the client 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)