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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
BNSF

BNSF Automotive Hub Operations API

The BNSF Automotive Hub Operations API covers haul-away gate operations at BNSF automotive ramps: gate entry requests submitted before an ingate, gate exit and pre-exit requests, holds placed on and released from a VIN at origin or destination, and gate-pass lookups by AAR ramp code and VIN. Seven operations, keyed on NMFTA SCAC and AAR ramp code, serving truckers, dispatchers and vehicle OEMs.

Documentation Provider Profile APIs.io OpenAPI GitHub

BNSF Automotive Hub Operations API is one of 8 APIs that BNSF publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Freight, Automotive, Hub, Gate Operations, and VIN. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 7 paths, and defines 9 schemas. It is described by OpenAPI 3.0.0, at version 1.0.

Requests are made against 2 base URLs: https://api.bnsf.com:6443, https://api-trial.bnsf.com:6443.

7 operations 7 paths 9 schemas 2 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0
Base URL
https://api.bnsf.com:6443
Authentication
Mutual TLS, Mutual TLS
Contact
BNSF Customer API
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

BNSF Automotive Hub Operations API declares 2 security schemes for authenticating requests. It requires mutual TLS (MutualTLS). It requires mutual TLS (Restricted). By default, every request must be authenticated.

  • MutualTLS — BNSF requires certificate-based mutual TLS (two-way authentication). Client certificates must be x509 PEM, issued by a recognised public Certificate Authority…
  • Restricted — Restricted Service. The same client certificate applies, but the certificate must additionally be authorised for this service by BNSF API Support. Unauthorised…

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 2 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Automotive Hub Operations 7
POST
/v1/pregate/automotive/haulaway-entry
Haul Away Gate Entry Request - Allow truckers and/or dispatchers to submit load details prior to an actual ingate for an automotive haul away move.
postV1PregateAutomotiveHaulawayEntry body → 200400403404405429500504
POST
/v1/vehicles/addHold
​​AddHold Request - Haulway or OEM will have the capability to add hold on VIN at Origin or Destination ("O" or "D")
postV1VehiclesAddhold body → 200400403404405429500504
POST
/v1/vehicles/releaseHold
​​Release Hold Request - This enables Haulway and OEM to release existing Hold on a VIN.
postV1VehiclesReleasehold body → 200400403404405429500504
GET
/v1/gate-pass/ramp/{aarRampCode}/vehicle/{vin}
Haulway Carries - Retrieves information of a entry request that is already posted.
getV1GatePassRampByAarRampCodeVehicleByVin 2 params → 200400403404405429500504
GET
/v1/gate-pass/ramp/{aarRampCode}/gate-pass/{gatePassCode}
Haulway Carries - Retrieves information of a entry request that is already posted.
getV1GatePassRampByAarRampCodeGatePassByGatePassCode 2 params → 200400403404405429500504
POST
/v1/exit-request
Haul Away Gate Exit Request – Allow truckers and/or dispatchers to submit load details AT outgate.
postV1ExitRequest body → 200400403404405429500504
POST
/v1/pre-outgate
Haul‑Away Gate Pre-Exit Request – Allow dispatchers to submit load details BEFORE ARRIVING to outgate the load for the dealer.
postV1PreOutgate body → 200400403404405429500504

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are haulawayGateEntryResponse (9 properties), haulawayGateEntryRequest (8 properties), gateExitRequestFromHaulaway (8 properties), GateExitRequestResponseFromBNSF (3 properties). Each schema is shown below with its type and property counts.

haulawayGateEntryRequest
object
8 properties 4 required
haulawayGateEntryResponse
object
9 properties 4 required
automotiveVehicleHoldAdd
object
3 properties 3 required
automotiveVehicleHoldRelease
object
2 properties 2 required
gateEntryRequestList
object
1 property
gateExitRequestFromHaulaway
object
8 properties 8 required
GateExitRequestResponseFromBNSF
object
3 properties
preOutageRequestFromHaulway
object
1 property
PreOutageResponseFromBNSF
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bnsf-automotive-hub-operations-openapi.yml Raw ↑

Other APIs BNSF publishes across the network.

BNSF Tracing API
AE Profile APIs.io
BNSF Intermodal Hub Operations API
AE Profile APIs.io
BNSF Prices and Rates API
AE Profile APIs.io
BNSF Schedules API
AE Profile APIs.io
BNSF Waybill Management API
AE Profile APIs.io
BNSF Reference Files API
AE Profile APIs.io
BNSF Diagnostics API
AE Profile APIs.io
#Freight#Automotive#Hub#Gate Operations#VIN#Logistics
← Back to B APIs
API Details
ID
bnsf:bnsf-automotive-hub-operations-api
Base URL
https://api.bnsf.com:6443
Docs
https://www.bnsf.com/ship-with-bnsf/support-services/customer-api/
Provider
BNSF
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=bnsf-automotive-hub-operations-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/bnsf-automotive-hub-operations-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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