#freight

The ISO 6346 size-and-type codes used to identify intermodal freight containers as an API — the reference a container booking system, EDI integration or terminal operating system needs. Every shipping container is described by a 4-character code (for example 22G1 = a 20-foot general-cargo container, 45R1 = a 40-foot high-cube reefer). For each of 700+ codes the API returns a human-readable description, the container length in feet, the height in feet and the ISO group code it belongs to. Look a code up, list every code in a group, search by description (reefer, tank, open top, flat rack…), or list the whole set. Served from memory — always fast.

api.oanor.com/containercodes-api

Freight and logistics maths as an API, computed locally and deterministically — the LTL freight class and load-planning numbers a shipper, broker or warehouse works to. The freight-class endpoint computes the density (weight ÷ cubic feet) of a shipment and maps it to the NMFC density-based freight class — the 18-band scale from class 50 (densest, cheapest) to 500 (lightest) — so a 200 lb pallet measuring 48×40×48 inches is 3.75 lb/ft³ and lands in class 250. The pallet endpoint palletizes a carton: it takes the better of the two footprint orientations for cartons per layer, fills the usable stack height in layers, and returns the cartons per pallet limited by the smaller of the cube and the weight cap, with the cargo weight and stack height (defaulting to a 48×40 GMA pallet). The container endpoint loads a 40-foot high-cube container (or any dimensions you give): how many units fit by axis-aligned stacking and by payload, which one is the limiting factor, the total weight and the cube utilisation. Everything is computed locally and deterministically, so it is instant and private. Ideal for logistics, freight-brokerage, 3PL, warehouse-management and supply-chain app developers, LTL rating and load-planning tools, and shipping calculators. Pure local computation — no key, no third-party service, instant. Imperial units (inches, pounds, cubic feet) as the NMFC scale is US-based. Live, nothing stored. 3 compute endpoints. This is freight-class and load-planning maths; for single-parcel courier billing weight use a dimensional-weight API.

api.oanor.com/freight-api