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 CARLOAD API

The CARLOAD API from BNSF — 3 operation(s) for carload.

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

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

This API exposes 4 operations across 3 paths, and defines 3 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.

4 operations 3 paths 3 schemas 3 GET1 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 4

Across 3 paths, the API surfaces 4 operations — 3 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

CARLOAD 4
GET
/v1/cars
Cars - Returns tracing details for railcars on the BNSF network, with a default…
getV1Cars 2 params → 200400403404405429500504
POST
/v1/cars
Cars - Returns tracing details for requested cars, up to 300 at a time
postV1Cars body → 200400403404405429500504
GET
/v1/carload-consist
Carload Consist - Returns tracing details for railcars on U, J, C, E, G and X…
getV1CarloadConsist 1 param → 200400403404405429500504
GET
/v1/trip-plan-carload
Trip Plan - Returns list of significant events planned for a railcar equipment…
getV1TripPlanCarload 2 params → 200400403404405429500504

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are carload (36 properties), tripPlan (4 properties). Each schema is shown below with its type and property counts.

equipment_list
array
carload
object
36 properties
tripPlan
object
Travel itinerary for rail equipment.
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bnsf-carload-api-openapi.yml Raw ↑

Other APIs BNSF publishes across the network.

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

This is an independent, third-party profile of BNSF CARLOAD 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.