BIC-Boxtech API

Transportation / OAuth Advanced HTTPS
Varies by plan (check documentation)

Overview

BIC-Boxtech provides technical specifications for shipping containers in the global fleet, including dimensions, tare weight, and capacity details. It is useful for logistics developers who need accurate container data for freight management systems. Authentication requires OAuth, so you will need to set up an OAuth flow before making requests.

Beginner Tip

Start by requesting an OAuth token from the BIC-Boxtech portal before calling any endpoints. Container data is identified by BIC codes (e.g., MSCU1234567), so make sure you have valid BIC codes to query.

Available Data

BIC-Boxtech data via REST API

Example Response

JSON Response
{
  "route": "Line 1",
  "origin": "Station A",
  "destination": "Station B",
  "departure": "08:30",
  "arrival": "09:15",
  "status": "On Time",
  "delays_min": 0
}

Field Reference

container_number The unique BIC container identifier following ISO 6346 format (e.g., MSCU1234567).
size_type ISO size and type code indicating container dimensions and type (e.g., 22G1 for a 20ft general purpose container).
tare_weight The empty weight of the container in kilograms.
max_gross_weight Maximum allowable total weight including cargo, in kilograms.
internal_volume Internal cubic capacity of the container in cubic meters.

Implementation Example

Request
const url = "https://docs.bic-boxtech.org/";
// Replace headers or query params with the values required by this API.
const response = await fetch(url, {
  headers: {
  "Authorization": "Bearer YOUR_API_KEY"
  }
});
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

401 Unauthorized Missing or expired OAuth access token
Re-authenticate using your OAuth client credentials to get a fresh access token before making requests.
404 Not Found The BIC container code does not exist in the database
Verify the container BIC code format (4 letters + 6 digits + 1 check digit) and ensure the container is registered in the global fleet.
400 Bad Request Malformed container code in the request
Check that the BIC code follows the ISO 6346 standard with correct prefix, serial number, and check digit.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth OAuth
HTTPS REQUIRED
CORS UNKNOWN
Category Transportation
Difficulty Advanced
Verified: 2026-04-04

Similar APIs

View All →