How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

BNSF Requests API

The Requests API from BNSF — 41 operation(s) for requests.

BNSF Requests API is one of 5 APIs that BNSF publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Requests. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 44 operations across 41 paths, and defines 43 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api.bnsf.com:6443.

44 operations 41 paths 43 schemas 3 DELETE14 GET27 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.bnsf.com:6443
Terms of Service
Resource Areas
1

Paths & Operations 44

Across 41 paths, the API surfaces 44 operations — 3 DELETE, 14 GET, 27 POST. Each is listed below with its method, path, parameters, and response codes.

Requests 44
POST
/v1/pregate/automotive/haulaway-entry
Haul Away Gate Entry Request - Allow truckers and/or dispatchers to submit load…
postV1PregateAutomotiveHaulawayEntry body → 200400403404405429500504
POST
/v1/vehicles/addHold
​​AddHold Request - Haulway or OEM will have the capability to add hold on VIN…
postV1VehiclesAddHold body → 200400403404405429500504
POST
/v1/vehicles/releaseHold
​​Release Hold Request - This enables Haulway and OEM to release existing Hold…
postV1VehiclesReleaseHold body → 200400403404405429500504
GET
/v1/gate-pass/ramp/{aarRampCode}/vehicle/{vin}
Haulway Carries - Retrieves information of a entry request that is already…
getV1GatePassRampByAarRampCodeVehicleByVin 2 params → 200400403404405429500504
GET
/v1/gate-pass/ramp/{aarRampCode}/gate-pass/{gatePassCode}
Haulway Carries - Retrieves information of a entry request that is already…
getV1GatePassRampByAarRampCodeGatePassByGatePassCode 2 params → 200400403404405429500504
POST
/v1/exit-request
Haul Away Gate Exit Request – Allow truckers and/or dispatchers to submit load…
postV1ExitRequest body → 200400403404405429500504
POST
/v1/pre-outgate
Haul‑Away Gate Pre-Exit Request – Allow dispatchers to submit load details…
postV1PreOutgate body → 200400403404405429500504
GET
/healthcheck
Check the status of the BNSF Customer API
getHealthcheck → 200400403404405429500504
POST
/v1/analytic-event
Submit event data for analytical purposes
postV1AnalyticEvent body → 200400403404405429500504
GET
/v1/dray-booking/open
Dray open booking details
getV1DrayBookingOpen 1 param → 200400403404405429500504
POST
/v1/dray-plan/list-units
Dray Plan List Units- Returns a list of dray plans for a given supplier633 and…
postV1DrayPlanListUnits 1 param body → 200400403404405429500504
DELETE
/v1/dray-plan/initial/{equipmentInitial}/number/{equipmentNumber}
Dray Plan- Remove dray plans
deleteV1DrayPlanInitialByEquipmentInitialNumberByEquipmentNumber 2 params → 200400403404405429500504
GET
/v1/dray-plan/units
Dray Plan- Capture an intermodal container's dwell profile from dray carriers…
getV1DrayPlanUnits 1 param → 200400403404405429500504
POST
/v1/dray-plan/units
Dray Plan- Create dray plans
postV1DrayPlanUnits 1 param body → 200400403404405429500504
POST
/v2/dvir
Driver Vehicle Inspection Report - Submit chassis defects (Y/N) within BNSF…
postV2Dvir body → 200400403404405429500504
POST
/v1/flips
Flips - Returns details on authorized flips for given units
postV1Flips body → 200400403404405429500504
GET
/v1/hub
Hub - Returns a list of valid lot locations at a given hub facility
getV1Hub 2 params → 200400403404405429500504
POST
/v2/ingate
Ingate - Returns way-billed units that can be registered prior to arrival at a…
postV2Ingate body → 200400403404405429500504
GET
/v1/ingate-management/current
Current Gate Target - Returns all ingate targets related to the authorized list…
getV1IngateManagementCurrent → 200400403404405429500504
POST
/v2/ingate/validate
Validate Ingate - Returns required/missing information needed for ingate
postV2IngateValidate body → 200400403404405429500504
POST
/v1/j1-receipts
J1 Receipts - Returns a list of J1 Gate Receipts
postV1J1Receipts body → 200400403404405429500504
POST
/v2/outgate
Outgate - Returns way-billed units that can be registered prior to exiting at a…
postV2Outgate body → 200400403404405429500504
POST
/v2/outgate/validate
Validate Outgate - Returns required/missing information needed for outgate
postV2OutgateValidate body → 200400403404405429500504
POST
/v1/pickup-number
Pickup Number - Validate and/or retrieve pickup numbers
postV1PickupNumber body → 200400403404405429500504
POST
/v1/pregate/in
Pre-Ingate - Advanced creation of an ingate ahead of arriving at a hub facility
postV1PregateIn body → 200400403404405429500504
DELETE
/v1/pregate/in
Cancel a pre-ingate
deleteV1PregateIn 4 params → 204400403404405429500504
POST
/v1/pregate/out
Pre-Outgate - Advanced creation of an outgate ahead of exiting a hub facility
postV1PregateOut body → 200400403404405429500504
DELETE
/v1/pregate/out
Cancel a pre-outgate
deleteV1PregateOut 4 params → 204400403404405429500504
POST
/v2/street-en-route
Street En-route - Report pre-arrival to hub and returns rail waybill ingate…
postV2StreetEnRoute body → 200400403404405429500504
POST
/v3/unit-details
Unit Details - Returns hub information (e.g., Lot Location) for units at a BNSF…
postV3UnitDetails body → 200400403404405429500504
GET
/v3/unit-details/domestic-empties
Domestic Empties - Returns a list of empty units ready for pickup at a BNSF…
getV3UnitDetailsDomesticEmpties 3 params → 200400403404405429500504
POST
/v1/update-parking
Update Parking - Update a unit's parking information at a Hub facility (i.e.
postV1UpdateParking body → 200400403404405429500504
POST
/v1/carload-rates
Carload Rates - Returns a list of prices within a BNSF Carload Price Authority
postV1CarloadRates body → 200400403404405429500504
POST
/v1/intermodal-rates
Intermodal Rates - Returns a list of prices within a BNSF Intermodal Price…
postV1IntermodalRates body → 200400403404405429500504
POST
/v1/invoices
​Retrieve Open Invoices - Returns details of customer's open invoices for given…
postV1Invoices body → 200400403404405429500504
POST
/v1/rail-miles
Rail Mile Inquiry API – Mileage – Returns mileage for BNSF local and/or rule 11…
postV1RailMiles body → 200400403404405429500504
GET
/v1/event-codes
Event Codes - returns a list of event codes and their descriptions, which…
getV1EventCodes → 200400403404405429500504
GET
/v1/stations
Stations - Returns details of each station matching input criteria
getV1Stations 4 params → 200400403404405429500504
GET
/v1/stcc
STCC - Returns STCC numbers and descriptions matching input criteria
getV1Stcc 2 params → 200400403404405429500504
GET
/v1/stcc/hazardous
STCC - Hazardous - Returns detailed information on hazardous materials matching…
getV1StccHazardous 2 params → 200400403404405429500504
POST
/v1/umler
Umler - The Umler service returns internal and external dimensions, capacities…
postV1Umler body → 200400403404405429500504
GET
/v1/intermodal-schedules
Intermodal Schedules - Returns all Intermodal Schedules
getV1IntermodalSchedules 3 params → 200400403404405429500504
POST
/v1/bol
Submit Bill of Lading - Submit required transit information in order to create…
postV1Bol body → 200201400403404405429500
GET
/v1/waybill
Retrieve Waybill - Retrieve current active waybill/bill of lading information…
getV1Waybill 2 params → 200400403404405429500504

Schemas 43

The contract defines 43 schemas that model the data the API accepts and returns. The most detailed are j1_receipt (87 properties), unit_information (44 properties), Intermodal_Pregate (22 properties), Gate_Move_Request (19 properties). Each schema is shown below with its type and property counts.

haulawayGateEntryResponse
object
9 properties 4 required
automotiveVehicleHoldAdd
object
3 properties 3 required
gateExitRequestFromHaulaway
object
8 properties 8 required
PreOutageResponseFromBNSF
object
2 properties
GateExitRequestResponseFromBNSF
object
3 properties
haulawayGateEntryRequest
object
8 properties 4 required
gateEntryRequestList
object
1 property
automotiveVehicleHoldRelease
object
2 properties 2 required
preOutageRequestFromHaulway
object
1 property
Generic_User_Provided_Details
object
4 properties 3 required
intermodalUnits
object
1 property
j1_receipt_response
object
3 properties
DrayPlan
object
1 property
Pickup_Number_Request
object
3 properties 2 required
DrayBookingResponse
object
3 properties
j1_receipt
object
87 properties
StreetEnRouteResponse
object
6 properties 3 required
j1_response
object
4 properties
Pickup_Number
object
2 properties
IngateResponse
object
3 properties
DvirInputBean
object
5 properties 5 required
drayBooking
object
12 properties
Gate_Move_Request
object
JSON document used to send and receive information related to a Customer's Drayage Booking requests.
19 properties 14 required
unit_information
object
44 properties
OutgateResponse
object
2 properties
IntermodalUnits
object
1 property
unit_list
array
equipmentFlip
object
1 property
Intermodal_Pregate
object
22 properties 10 required
unit_location
object
3 properties
Intermodal_Station
object
Contains information related to Intermodal Stations and any details related to them.
3 properties 2 required
customerInvoice
object
7 properties 1 required
Price_Authority
object
1 property
prices_response
object
3 properties
OD_Pairs_Response
object
1 property
stcc
array
umler
array
hazardousCommodities
array
station
array
tripPlan
object
4 properties
intermodal_schedules
object
17 properties
billOfLading
object
1 property
Waybill_Details
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bnsf-requests-api-openapi.yml Raw ↑

Other APIs BNSF publishes across the network.

BNSF AUTOMOTIVE API
BNSF CARLOAD API
BNSF INTERMODAL API
BNSF TRAINS API
Where this information came from

This is an independent, third-party profile of BNSF Requests API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.