generated: '2026-09-06'
method: searched
source: >-
  Registry searches against registry.npmjs.org, pypi.org, rubygems.org and the GitHub repository
  search API, plus a full read of BNSF's seven API Center pages, on 2026-09-06.
description: >-
  BNSF publishes no client libraries in any language. There is no SDK page, no code samples section
  and no GitHub organisation. The only integration tooling BNSF documents is Postman — and it
  documents it as manual setup instructions, not as a downloadable collection.
package_count: 0
official_package_count: 0
packages: []
searched:
- registry: npm
  query: bnsf
  version: null
  published: null
  result: >-
    No first-party package. The only matches are unrelated third-party projects such as
    generator-bnsf, a 2015 Yeoman generator by an unaffiliated author.
- registry: pypi
  query: bnsf
  version: null
  published: null
  result: 404 Not Found.
- registry: rubygems
  query: bnsf
  version: null
  published: null
  result: 'Not found — the registry answered: This rubygem could not be found.'
- registry: github
  query: bnsf railway
  version: null
  published: null
  result: >-
    4 repositories, none owned by BNSF. No github.com/bnsf or github.com/bnsf-railway organisation
    exists.
- registry: docs
  query: BNSF API Center — Home, Getting Started, Catalog, Developer's Console, Push Notifications,
    Registration, API Support
  version: null
  published: null
  result: >-
    No SDK, library, package or download link on any page.
integration_tooling_documented:
- name: Postman
  official_collection_published: false
  version: null
  published: null
  note: >-
    BNSF's Getting Started page walks a caller through configuring a client certificate in Postman
    and hand-building a GET https://api-trial.bnsf.com:6443/v1/cars request. No .postman_collection
    file is published and no public Postman workspace is linked, so this is instructions, not a
    distributed artifact — hence version null.
- name: Swagger UI
  official: true
  version: v2.2
  published: null
  note: >-
    BNSF hosts Swagger UI 2.2 assets under
    /ship-with-bnsf/support-services/customer-api/v2.2/ to render its own Developer's Console. This
    is BNSF consuming a library, not publishing one; the distribution is unpinned static files on
    BNSF's own host with no registry metadata, so no publication date can be read. Recording it
    because the pinned v2.2 path is a currency signal in its own right: Swagger UI 2.x predates
    OpenAPI 3.0, which is the version of the documents it is rendering.
consequence: >-
  Every BNSF integration is hand-written against raw HTTP with a client certificate. There is no
  first-party abandonment signal to read here, because there is nothing published to go stale — the
  absence is total rather than decayed.