API for Express Release

Parse Sea Waybills into structured JSON via API

Send any SWB document to the KabyTech API and receive 35+ validated fields back as structured JSON. Non-negotiable document handling, express release data extraction, and UN/LOCODE port validation — all in a single API call.

SWB API — Ingest
EndpointPOST /v1/parse/swb✓
Content-Typemultipart/form-data✓
DocumentEGLV-BKK-240892.pdf✓
Carrier DetectedEVERGREEN✓
StatusPARSING✓
Ingest

Accept SWB in any format

Upload scanned Sea Waybills, carrier-generated PDFs, or EDI messages. The API accepts multipart form data and returns a parsed JSON response within 2 seconds. No per-carrier template required — Evergreen, ONE, MSC, and Maersk formats all handled automatically.

PDF uploadImage OCREDI parsingMulti-carrierExpress releaseBatch mode
SWB Parsed Response
SWB NumberEGLV-BKK-240892✓
ShipperTHAI RUBBER EXPORT CO LTD✓
ConsigneePT INDO POLYMER✓
POLTHLCH (Laem Chabang)✓
PODIDJKT (Jakarta)✓
VesselEVER LUCKY / 0412S✓
ContainerEISU9012345 [40HC]✓
Express ReleaseYES✓
Extract

35+ fields returned as structured JSON

The API extracts shipper, consignee, notify party, vessel/voyage, port of loading, port of discharge, container numbers, seal numbers, cargo description, weight, and freight terms. Express release flags and non-negotiable status are explicitly returned. Container numbers are validated with ISO 6346 check-digit logic.

Shipper/ConsigneeVessel/VoyagePort codesContainersFreight termsExpress release flag
SWB Validation Report
Port CodesTHLCH / IDJKT — VALID✓
Container CheckEISU9012345 — ISO 6346 PASS✓
Vessel MatchEVER LUCKY — CONFIRMED✓
Confidence98.4%✓
Warnings0✓
Validate

UN/LOCODE and ISO 6346 checks built in

Every parsed SWB goes through automatic validation: port codes checked against the UN/LOCODE registry, container numbers verified with ISO 6346 check-digit logic, and vessel names cross-referenced. Validation results are returned inline so your system can flag issues before they reach customs.

UN/LOCODE checkISO 6346 verifyVessel lookupConfidence scoresError flagsCustoms-ready
API Performance

SWB API throughput metrics

35+
Fields extracted per SWB
<2s
Average parse time
98.4%
Field-level accuracy
99.9%
API uptime SLA
FAQ

Sea Waybill API — Frequently Asked Questions

What is the difference between a Sea Waybill and a Bill of Lading?
A Sea Waybill (SWB) is a non-negotiable transport document that allows express release — cargo can be released to the named consignee upon vessel arrival without surrendering an original document. The KabyTech API extracts the express release flag and non-negotiable status automatically.
Which carriers are supported?
The API supports SWBs from all major ocean carriers including Evergreen, ONE, MSC, Maersk, COSCO, Hapag-Lloyd, Yang Ming, and regional carriers operating through Thai ports. No per-carrier configuration is required.
How many fields does the API extract from a Sea Waybill?
The API extracts 35+ fields including shipper, consignee, notify party, vessel/voyage, POL, POD, container numbers, seal numbers, cargo description, gross weight, measurement, freight terms, and the express release indicator.
Does the API validate container numbers?
Yes. Every container number is validated with ISO 6346 check-digit logic. Port codes are verified against the UN/LOCODE registry. Validation results are returned inline with each parsed field.
Can I process multiple SWBs in a single API call?
Yes. The batch endpoint accepts up to 50 SWB documents per request. Each document is processed independently and results are returned as an array of parsed records.

Ready to integrate SWB parsing into your system?

Get your API key and start parsing Sea Waybills in minutes. Full SDKs for Node.js, Python, and Java.

Get API KeyRead API Docs