D/O Intelligence API

Parse Delivery Orders for terminal release in seconds

Extract 25+ fields from Delivery Order documents via a single REST endpoint. Terminal codes, container numbers, release authorization, and cargo details — structured JSON returned in under 2 seconds. Built for Laem Chabang and Bangkok Port operations.

D/O Extracted Fields
D/O NumberDO-LCB-2026-04821
VesselOOCL BANGKOK V.026E
ContainerOOLU7654321
Seal No.TH20260412
TerminalLCMT-A (Laem Chabang)
StatusRELEASED
Field Extraction

25+ fields parsed from every Delivery Order

The D/O API extracts all critical fields from Delivery Order documents: D/O number, shipping line, vessel and voyage, container numbers, seal numbers, cargo description, gross weight, measurement, consignee details, and terminal release authorization codes.

Port-specific fields for Laem Chabang (Terminal A/B/C/D) and Bangkok Port (Klong Toey) are mapped automatically. Every field includes a confidence score for downstream validation.

D/O NumberContainer No.Seal NumberVessel & VoyageTerminal CodeRelease Auth
Terminal Coverage
LCMT-ASupported
LCMT-B (Evergreen)Supported
LCMT-C (TIPS)Supported
LCMT-D (Hutchison)Supported
Bangkok PortSupported
Port Terminal Coverage

Laem Chabang and Bangkok Port formats supported

The API handles D/O documents from all major Thai port terminals: Laem Chabang Terminal A (LCMT-A), Terminal B (Evergreen), Terminal C (TIPS), Terminal D (Hutchison), and Bangkok Port at Klong Toey.

Each terminal issues D/Os in slightly different formats. The KabyTech OCR engine recognizes all variants and normalizes the output to a consistent JSON schema — no per-terminal configuration required.

Laem Chabang A/B/C/DBangkok PortMulti-format OCRNormalized JSONTerminal auto-detect
Release Status
Customs ClearedYES
Terminal ChargesSETTLED
Release AuthREL-20260412-0093
Pickup Window12 Apr 06:00–18:00
Release Workflow

Track authorization status from issuance to cargo release

Every parsed D/O includes release status fields: whether the cargo has been cleared by customs, whether terminal charges are settled, and the final release authorization code. These fields let your system automatically track where each container stands in the release process.

Combine D/O API data with your TMS or WMS to trigger container pickup scheduling the moment release authorization is confirmed.

Release statusCustoms clearance flagTerminal chargesPickup triggerWebhook callback
By the Numbers

D/O API performance metrics

25+
Fields extracted per D/O
97.5%
Field-level accuracy
<2s
Average response time
5
Thai port terminals supported
FAQ

Frequently asked questions

What document formats does the D/O API accept?
The API accepts scanned PDFs, digital PDFs, JPEG, PNG, and TIFF images of Delivery Orders. Documents from all major Thai port terminals are supported. Minimum recommended resolution is 150 DPI, with 300 DPI for best accuracy.
Which port terminals are covered?
Laem Chabang Terminal A (LCMT-A), Terminal B (Evergreen), Terminal C (TIPS), Terminal D (Hutchison), and Bangkok Port (Klong Toey). New terminals are added regularly — contact us if you need a specific terminal.
Can the API track release authorization status?
Yes. The parsed response includes customs clearance status, terminal charge settlement, and the release authorization code. Use webhook callbacks to get notified the moment a D/O status changes.
How does pricing work?
Pricing is per API call. The Starter plan includes 500 calls/month free. Professional plans start at 5,000 calls/month. Enterprise plans offer unlimited volume with custom pricing.
Does the API handle bilingual Thai/English D/Os?
Yes. The KabyTech OCR engine processes Thai and English text natively, including bilingual documents common at Thai port terminals. No language parameter is required — detection is automatic.

Ready to automate D/O processing?

Book a demo and we will process your actual Delivery Order documents live — or start a free trial and integrate in under 10 minutes.