EDGE ENGINE Sub-2ms Deterministic V8 Execution • Zero Data Retention Explore API Specs →
Latency: <1ms Edge Availability: 99.99% Standard: ISO 6346 Table 4 & 5 V8 Pure Compute

ISO 6346 4-Character Container Size and Type Code Directory

Decode ISO 6346 4-character size and type codes into precise metric and imperial dimensions and cargo types.

Official Regulatory Standard & Verification Protocol Authority: Bureau International des Conteneurs (BIC) & ISO ↗

Quick Technical Summary: Decode ISO 6346 4-character size and type codes into precise metric and imperial dimensions and cargo types. Implementation conforms to ISO 6346 / BIC Container Prefix Coding.

Execution SLA
<1ms Edge (Cloudflare V8)
Governing Norm
ISO 6346 Table 4 & 5
Throughput Limit
512 KB / Payload
Data Privacy
100% In-Memory (Zero Store)

Specification & Structural Breakdown

The 4-character size/type code indicates container length (1st char), height/width (2nd char), and container type with special features (3rd and 4th chars).

CodeLengthHeightType
22G120 ft (6.058 m)8 ft 6 in (2.591 m)General Purpose Container
42G140 ft (12.192 m)8 ft 6 in (2.591 m)General Purpose Container
45G140 ft (12.192 m)9 ft 6 in (2.896 m High Cube)General Purpose Container with ventilation
45R140 ft (12.192 m)9 ft 6 in (High Cube)Refrigerated Thermal Container (Reefer)
22U120 ft (6.058 m)8 ft 6 inOpen Top Container
22T120 ft (6.058 m)8 ft 6 inTank Container for liquids
Interactive Edge Validator

Test ISO 6346 4-Character Container Size and Type Code Directory Live

Paste raw inputs up to 32KB and inspect deterministic parsed JSON in real-time across 330+ Cloudflare edge locations. Pure compute, zero cold-starts.

Launch Workbench →

Parsed JSON Response Model

The edge microservice transforms input payloads into strongly-typed hierarchical JSON with zero cold starts:

HTTP 200 JSON Payload
{
  "code": "45G1",
  "lengthFeet": 40,
  "heightFeet": 9.5,
  "type": "General Purpose High Cube"
}

Copy-Paste Integration Code

Integrate this validator directly into your application using your production API key:

cURL
curl --request POST \
  --url "https://iso-6346-container-chassis-check-digit-validator.stanzaapi.com/api/v1/container/validate" \
  --header "Content-Type: application/json" \
  --header "x-api-key: YOUR_API_KEY" \
  --data '{
  "containerNumber": "CSQU3054383",
  "sizeTypeCode": "45G1"
}'
Node.js (Fetch)
const response = await fetch("https://iso-6346-container-chassis-check-digit-validator.stanzaapi.com/api/v1/container/validate", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "x-api-key": process.env.API_KEY || "YOUR_API_KEY"
  },
  body: JSON.stringify({
  "containerNumber": "CSQU3054383",
  "sizeTypeCode": "45G1"
})
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests
import json

url = "https://iso-6346-container-chassis-check-digit-validator.stanzaapi.com/api/v1/container/validate"
headers = {
    "Content-Type": "application/json",
    "x-api-key": "YOUR_API_KEY"
}
payload = {
    "containerNumber": "CSQU3054383",
    "sizeTypeCode": "45G1"
}

response = requests.post(url, json=payload, headers=headers)
print(response.json())
Go
package main

import (
	"bytes"
	"fmt"
	"io"
	"net/http"
	"os"
)

func main() {
	url := "https://iso-6346-container-chassis-check-digit-validator.stanzaapi.com/api/v1/container/validate"
	payload := []byte(`{"containerNumber":"CSQU3054383","sizeTypeCode":"45G1"}`)

	req, _ := http.NewRequest("POST", url, bytes.NewBuffer(payload))
	req.Header.Add("Content-Type", "application/json")
	req.Header.Add("x-api-key", os.Getenv("API_KEY"))

	res, err := http.DefaultClient.Do(req)
	if err != nil {
		panic(err)
	}
	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)
	fmt.Println(string(body))
}

Frequently Asked Questions & Technical Notes

What does the 4th digit in 45G1 indicate?

The 4th character describes specific features like passive ventilation openings.

Related ISO 6346 Container & Chassis Check-Digit Validator API Formats

Explore sibling specifications and standards in the same developer cluster: